2 What’s New in this Release

This chapter describes the features, enhancements, and changes made to Oracle GoldenGate. Oracle updates the release notes periodically after the software release. This document is accurate at the time of publication.

New Features

This section describes the features and enhancements made to Oracle GoldenGate.

Release 19c (19.1.0) - May 2019 Initial Release

Reducing supplemental logging overhead in Oracle Database 19.1 for Oracle GoldenGate

New supplemental logging syntax was added in Oracle Database 19.1.

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA SUBSET DATABASE REPLICATION

When the source database is configured with subset database replication, supplemental redo will be generated based on schema and table-level TRANDATA settings.

Overhead for schema-level supplemental logging can be reduced by issuing DELETE TRANDATA for tables within a schema that are not required for replication.

Managing Encryption Using a Key Management Service in Oracle GoldenGate Microservices Architecture

Oracle GoldenGate Microservices Architecture provides integration with various Key Management Services (KMS) such as OCI and Oracle Key Vault to centralize and manage encryption keys. See Using a KMS with Oracle GoldenGate MA.

Target-Initiated Paths

Target-initiated paths for microservices enable the Receiver Server to initiate a path to the Distribution Service on the target deployment and pull trail files. This feature allows the Receiver Server to create a target initiated path for environments such as Demilitarized Zone Paths (DMZ) or Cloud to on-premise, where the Distribution Server in the source Oracle GoldenGate deployment cannot open network connections in the target environment to the Receiver Server due to network security policies.

New Admin Client Commands
The following Admin Client commands are added to Oracle GoldenGate 19c (19.1.0) to work with target-initiated distribution paths:
  • ADD RECVPATH

  • START RECVPATH

  • STOP RECVPATH

  • DELETE RECVPATH

  • INFO RECVPATH:

  • ALTER RECVPATH

The following commands are added to connect to an Oracle GoldenGate deployment using an Oracle wallet that contains the user credentials:
  • ADD CREDENTIALS

  • INFO CREDENTIALS

  • DELETE CREDENTIALS

The command UPGRADE HEARTBEATTABLE is available to alter heartbeat table generated by the ADD HEARTBEATTABLE command using a previous Oracle GoldenGate release.

The following commands have been added to allow users with security role to enable and disable services for any update operation by non-secure users.
  • DISABLE SERVICE

  • ENABLE SERVICE

New column conversion function @BINTOBASE64
New column conversion function to convert supplied binary data into BASE64 text.
New REST Endpoint to Retrieve Active Transactions and Current SCN Details
The REST Endpoint retrieves active transactions and current SCN details, which are used to determin the instantiation SCN required for Extract Initial Load setup.
Purge Trail Task that Allows Purging All Trails
The purge trail option has been enhanced to allow purging all trails using the Purge All Trails task option in the Administration Server. This features would help in applications such as Oracle Key Vault and sharding where multi-master replication will be automatically set up and the default option would be to purge all trails. This option would also be useful for migration classic architecture and as an alternate to using the PURGEOLDEXTRACTS option.
UPSERT Operation Support
UPSERT operation type support is available. An UPSERT operation works like an INSERT operation however, if an INSERT row already exists, the operations changes to UPDATE instead of INSERT.
New HEARTBEATTABLE Option
The UPGRADE HEARTBEATTABLE option is now available for heartbeat tables from the GGSCI Command Interface:
Oracle
Track the Source Extract Position (LOGBSN) and Propagate to the Replication Targets

This feature allows the current Extract restart position (LOGBSN) to allow Replicats to maintain a more recent source LOGBSN and minimize the redo retention periods, This enhancement is enabled by default for new heartbeat tables. Existing heartbeat tables are upgraded. to support this enhancement. The enhanced heartbeat tables interoperate with heartbeat tables in deployments running older version of the Oracle GoldenGate

With more recent LOGBSNs, you can configure deleting tombstone tables for Automatic Conflict Detection Resolution (ACDR) tables (an Oracle-to-Oracle CDR feature) to be purged more aggressively.

Cross Endian Support for Remote Integrated Extract
Cross endian interoperability for Integrated Extract is automatically enabled when the endianess of the server where the Integrated Extract is running is different from the endianess of the server where the Oracle instance is running.
DB2 for i
Support for TIMESTAMP (12)
Oracle GoldenGate for DB2 for i now supports TIMESTAMP (12)
DBOPTIONS Parameter USEDATABASEENCODING

The DBOPTIONS USEDATABASEENCODING parameter is introduced to allow Extract to store all text data in the trail in its native character encoding for non-DBCS data.

TRANLOGOPTIONS BUFSIZE Parameter is available with DB2 for i

The TRANLOGOPTIONS BUFSIZE parameter is available with DB2 for i.

Improved Extract throughput

Extract efficiency has been substantially improved over previous releases. Throughput is enhanced while reducing overall processing resources for the same workload.

Difference in throughput between the default conversion of text to UNICODE and ‘COLCHARSET(PASSTHRU,*’), which does not convert text, has been substantially reduced for Oracle GoldenGate supported character sets.

Security Options

AES encryption, credential store, and Oracle Wallet are now available.

TRANLOGOPTIONS MAXAUTOCMTTRANSSIZE

This parameter sets the maximum number of records that are included in an implicitly created transaction. This affects the maximum number of records that are not part of an explicit transaction (have a 0 CCID) can be grouped together into a single implicit transaction.

CSN Requirements

System sequence number is no longer required for single journal Extracts. It is recommended that you use RCVSIZOPT(*MAXOPT3) for their journals to enable a full 64-bit journal sequence number which will eliminate the need to reset journal sequence numbers periodically.

DECFLOAT data type
DECFLOAT data type is supported.
Long Running Transactions (LRT) support
LRT features SHOWTRANS, SKIPTRANS, FORCETRANS are supported.
MySQL
Two-way SSL Support in MySQL Capture and Delivery
Oracle GoldenGate for MySQL supports an SSL connection of Extract or Replicat to the MySQL database server.
MySQL 8.0 Support
Oracle GoldenGate supports MySQL 8.0.
DB2 LUW
Support for TIMESTAMP (12)
Oracle GoldenGate for DB2 LUW now supports TIMESTAMP (12)
DECFLOAT data type
DECFLOAT data type is supported.
LRT support
LRT features SHOWTRANS, SKIPTRANS, FORCETRANS is supported.
DB2 z/OS
Online Schema Change Support

Support for online TABLE CREATE, DROP and ADD, ALTER, DROP COLUMN commands in the Extract without stopping and restarting the Extract to get the new table metadata for the Extract. Full table version history is supported.

Support for TIMESTAMP (12)
Oracle GoldenGate for DB2 z/OS supports TIMESTAMP with TIMEZONE
LRT support
LRT features SHOWTRANS, SKIPTRANS, FORCETRANS is supported.

Default Behavior Changes

This section describes the default behavior changes made to Oracle GoldenGate in relation to the last release.

Release 19c (19.1.0) - May 2019 Initial Release

TIMESTAMP with TIMEZONE with region ID

TIMESTAMP with TIMEZONE with region ID data is now supported for FETCH and initial load.

Trail File Format

After Extract update, if a newer trail file format is specified then the primary Extract will automatically rollover to the next trail file and writer in the specified trail file format. There is no need to run the ALTER EXTRACT ETROLLOVER command.

Extract Default Trail File Version
The primary Extract writes trail file in the same format as existing trail file format when you upgrade to Oracle GoldenGate 19c, unless you explicitly specify the trail file format version using the FORMAT RELEASE option. This behavior change prevents subsequent Replicat to abend if replicat is not upgraded.
Oracle TIMESTAMP WITH TIME ZONE capture
TIMESTAMP with TIMEZONE with region ID data is now supported for FETCH and initial load. For details, see TRANLOGOPTIONS in Reference for Oracle GoldenGate
GETCTASDML option default setting
GETCTASDML option available with TRANLOGOPTIONS parameter is enabled by default.
NOALLOWNULLABLEKEYS default setting
The default setting for the NOALLOWNULLABLEKEYS parameter is set to true.
Change in Binlog Format Support

Capture silently ignores the binlog events that are not written in the ROW format instead of abending when it detects a binlog_format other than ROW.

Deprecated Features

This section describes the deprecated and no longer supported features of Oracle GoldenGate.

Release 19c (19.1.0) - May 2019 Initial Release

ADD HEARTBEATTABLE NOADDTRANDATA

NOADDTRANDATA option of ADD HEARTBEATTABLE has been deprecated.

Oracle Database
TRANLOGOPTIONS INCLUDEREGIONID

TRANLOGOPTIONS INCLUDEREGIONID parameter is deprecated. The parameter is not required to capture Oracle TIMESTAMP with TIME ZONE with region ID time zone value. If the parameter is specified, a warning message is issued at startup.

TIMESTAMP with TIMEZONE with region ID data is now supported for FETCH and initial load. For details, see TRANLOGOPTIONS in Reference for Oracle GoldenGate.