What's new in HCL OneDB 2.0.0.0

Cloud Native

• The HCL OneDB 2.0.0.0 Cloud Native solution includes:
  • Docker Containers (OneDB server, Explore, REST Listener, MongoDB Listener, Connection Manager).
  • Helm Charts.
  • Kubernetes operator to coordinate high availability and backup & restore.
• User personas now include Kubernetes admins, in addition to DBAs.

Cloud Native High Availaility

• Kubernetes operator-enabled high availability node deployment (simple scale-out with failover):
  • Scale out using OneDB High Availability Data Replication (HDR) and Remote Standalone Secondaries (RSS) .
  • Auto scale out based on database workload or scales out to predetermined number of nodes:
    • OneDB images scale out from 2 nodes to 10 via configuration
• Two (or more) Connection Managers for connectivity redundancy.
• Failover coordinated with OneDB Connection Manager.
• Automatic failover if primary server does not come up cleanly upon restart.

Cloud Native Backup and Restore

• K8S Operator-enabled Backup & Restore solution using K8S managed persistent storage or cloud provider managed storage.
• Database backups to persistent volume using an NFS operator or cloud provider’s native storage, with the last three backups retained.
• Ability to restore the database from backup via configuration.

Enterprise Replication and High availability Enhancements

• Enterprise replication performance enhancements:

  Improvements are made to end to end ER performance to improve replication throughput and reduce latency. Most of the changes are internal to the server related to reducing internal latch contention and improve apply parallelism. External visible changes include, Enterprise replication now uses SMX transport mechanism for data replication to peer ER server which allows usage of multiple network pipes(configured using SMX_NUMPIPES) to send data to peer server. Also as part of send queue optimization, smaller transactions with size less than 26KB are now spooled to in-row transaction header table in syscdr database(configured using CDR_DBSPACE) instead of to smartblob space configured using CDR_QDATA_SBSPACE.

  For SMX related information, see Configure SMX connections and for CDR_DBSPACE configuration, see CDR_DBSPACE Configuration Parameter

  .
• Limitations on admin() commands on read only secondary:

  When connected to a secondary node, the admin() function is disabled and will always return a value of -1. In addition, the task() function will return an error for commands that involve modifying disk structures, since these administrative actions are meant to be executed only on primary or standalone nodes. See SQL Administration API Overview and admin() and task() Function Return Codes.

• New replication utility cdr check catalog added to verify metadata information across the servers. The cdr check catalog command compares the metadata information related to servers, replicates and replicate sets on replication servers for any inconsistency. See cdr check catalog.
• New configuration parameter SEC_NONBLOCKING_CKPT is introduced to enable non-blocking checkpoint at HDR and RS secondary server. See SEC_NONBLOCKING_CKPT configuration parameter.

Security Related Enhancements

• Auditing enhancement, support for Audit to Syslog (ASL) facility.
• Distributed transactions and PAM authentication enhancement.

Backup & Restore Enhancement

• It is now possible to take archives and log backups on a Remote Secondary Server (RSS) node using onbar utilty. An archive taken locally on this node may be used to recreate the RSS node and may also be used to restore a primary node in the event that no preferable archive exists. See Backup and Restore Guide.

Time series enhancement

• CountIf() functionality is extended with three new functions, GetMatchingIf, GetElementsIf and GetNULLElementsIf. See Time series SQL routines

CSDK enhancements

• New .NET Entity Framework Core Provider is released with OneDB 2.0.0.0.
• Few database utilities shipped with CSDK.

See OneDB .NET EF(Entity Framework) Core Provider Guide.

OneDB Explore enhancements

• Schema manager has been enhanced with Create and Drop table capability.
• OneDB Explore server and agent logging behavior customization (change the logging level, log file location, enable rolling window logging) using server.log4j.xml and agent.log4j.xml.
• Provision is made for user to specify connection properties for OneDB Explore agent separately.
• Added HCL OneDB Explore APIs.

Other 2.0.0.0 Enhancements

• New session environment variable DBINFO_DBSPACE_RETURN_NULL_FOR_INVALID_PARTNUM added to specify if dbinfo('dbspace', partnum) raises an error -727 or returns NULL when an invalid partition number (partnum) is provided. See DBINFO_DBSPACE_RETURN_NULL_FOR_INVALID_PARTNUM environment variable.
• DBSPACETEMP configuration parameter now allows spaces with mixed page sizes. See DBSPACETEMP configuration parameter.
• onstat -g laq enhancement to print information about log recovery apply queues which includes logical log recovery on secondary servers as well as logical restore or logical recovery part of fast recovery. See onstat -g laq command: Print log apply queues.
• New SMI table syssessiontempspaceusage table contains information about each session's temp space usage. See syssessiontempspaceusage.
• TEMPTAB_NOLOG is enhanced to have value 2 (earlier supported values were 0 and 1). When set to 2, it enables logical logging on temporary table operations for primary server and disables logical logging on temporary table operations for secondary servers(HDR, RSS and SDS). On primary/standard server, same behavior as 0, on secondary servers, same behavior as 1. When server type changes, logging for temporary tables will be enabled/disabled depending on the current server role. See TEMPTAB_NOLOG configuration parameter.
• New DSN option UPDATE_DESCRIBE or UPDDESC and Connection Property SQL_INFX_ATTR_UPDATE_DESCRIBE is added for BLOB/CLOB data types, because these data types need special handling in the ODBC Driver for setting up BLOB/CLOB context in the driver and require details of these data types description from the server. By enabling this option Server will send the description of these data types which will be used by ODBC Driver. See Configuring a new user DSN or system DSN.

Migration enhancement

Removed Features