Default Behavior Changes

Release 21c (21.19.0.0.0) - July 2025

Bug 37757820: Generic - Enable NOCHECKUNIQUEKEYS as Default for BATCHSQL for all non-Oracle Databases

Enabled NOCHECKUNIQUEKEYS as default for BATCHSQLfor all the non-Oracle databases.

Bug 37909236: MySQL - Extract fails when MariaDB has binlog_annotate_row_events variable enabled

Starting with this version of Oracle GoldenGate, the requirement to set binlog_annotate_row_events to OFF has been removed for MariaDB.

Release 21c (21.15.0.0.0) - October 2024

Oracle GoldenGate Wallets Security Update

Auto-login property removed from the Oracle GoldenGate wallets

To enhance the security of Oracle GoldenGate wallets that store credential information (login information of Microservices users), the auto-login property of Oracle GoldenGate wallets has been removed.

As a result, after the deployment has been patched to Oracle GoldenGate release 21.15 and higher and started, rolling back to the previous Oracle GoldenGate release of 21.14 or lower, is not feasible as the password protected wallets cannot be converted back to auto-login wallets automatically.

A short-term workaround to get the information stored in the wallets before patching to Oracle GoldenGate Release 21.15 or higher, is to save the auto-login wallets from the earlier version and manually restore these wallets on a rollback.

Release 21c (21.15.0.0.0) - July 2024

MySQL - Removed the remote (RMTTRAIL) option from the WebUI: For MySQL, the Remote button that was used to add an Extract, has been removed from the WebUI.

Release 21c (21.14.0.0.0) - April 2024

PostgreSQL - Capture and delivery support for base partitioned tables

For PostgreSQL, capturing from base partitioned tables is now supported. This is a change from the previous version of Oracle GoldenGate where Extract might have been configured to capture directly against inidividual partitions, such as TABLE schema.basetable_part1 or TABLE schema.basetable_part2.

If you have configured the Extract to capture from PostgreSQL individual partitions in earlier versions of Oracle GoldenGate and are now upgrading or patching to Oracle GoldenGate 21.14 or after, you need to perform steps specified in Doc ID 3017127.1 to avoid data loss.

Release 21c (21.10.0.0.0) - April 2023

Oracle Database and MA Deployments

Opatches bundled with JDK for all Oracle and Microservices Architecture deployments

The JDK is now packaged in the Oracle GoldenGate patch starting release version 21.10 and 19.1.0.0.230418. Please note that only <GG_HOME>/jdk directory is updated with the GoldenGate patch releases. See Doc ID 2359395.1 for more information and additional references for updating JDK either through GoldenGate patch or independently.

You still have the option to install the latest JDK patch into <GG_HOME>/jdk directory independently at any time. See Doc ID 1492980.1 for more information.

Release 21c (21.4.0.0.0) - October 2021

SQL Server

For Oracle GoldenGate Microservices Architecture installations against a source SQL Server database, the Oracle GoldenGate CDC Cleanup job has been replaced with a new Purge Change Data task. A new task is required for Extract to run.

You can create the task from the Administration Service, Configuration, Tasks tab. Create the task after enabling supplemental logging for the tables in a source database and prior to starting the Extract.

: Oracle GoldenGate Replicat for SQL Server no longer supports OLE DB and Replicat will only use ODBC for its connectivity and to deliver DML operations, and if connecting with the Microsoft ODBC Driver 17 for SQL Server, version 17.8.1 or newer, Replicat will set the connection as the Replication User automatically, which replaces the need to use the DBOPTIONS USEREPLICATIONUSER parameter.

Release 21c (21.3.0) - August 2021

DB2 for i: For DB2 for i, the ADD HEARTBEATTABLE command has been enhanced to handle upgrade or misconfiguration of heartbeat table functionality. Now, you can run the ADD HEARTBEATTABLE command again to repair the functionality of an existing heartbeat table setup without deleting the existing heartbeat data.

SQL Server

Extract for SQL Server no longer abends when DDL changes are made to the underlying user tables. In prior releases, if the Extract encountered a mismatch between the user table metadata and the CDC Capture Change Tracking table metadata, due to columns added after TRANDATA was enabled for the table, the Extract would abend. From Oracle GoldenGate 21c (21.3.0) onward, Extract will not abend when table changes are made to the user table. It will continue to process the data as it exists in the CDC Capture Change Tracking table.

This allows the Extract to continue to run when DDL changes occur, but you should use governance to properly handle DDL changes so that Extract can pick up the data for changed columns.

For more information, see the Requirements for Table Level DDL Changes in the SQL Server chapter of the Using Oracle GoldenGate for Heterogeneous Databases guide.

Release 21c (21.1.0) - Initial Release May 2021

Oracle GoldenGate binaries are no longer installed on a shared drive: Oracle always recommended installing the Oracle GoldenGate binaries (OGG_HOME) on a local file system as a best practice. From this release onward, it is a requirement. The binaries must be installed on local drives. For more information refer to MOS note DOC ID 2689857.1.

Simplified heartbeat administration for Oracle Databases: Heartbeat table administration operations are only be done in the schema of the DBLOGIN user. GGSCHEMA is now only required for CDB root Extracts.

Logging of full metadata enabled when upgrading from Oracle GoldenGate 19c to 21c and the database is MySQL 8.0: This change is applicable when upgrading from Oracle GoldenGate 19c to 21c with MySQL 8.0.; However, for upgrading Oracle GoldenGate 19c to 21c with MySQL 5.7 no change is required.

Table containing IDENTITY columns with default sequence needs to be created with primary key

For Oracle database, table with identity column needs to be created with primary key, otherwise the Replicat will abend with errors similar to the following:

2020-02-07 08:17:53 ERROR OGG-00516 Fatal error executing DDLreplication: error [Error code [1430], ORA-01430: column being added already exists intable]

One shiphome supporting all Oracle Database versions: Instant Client 21c is bundled with Oracle GoldenGate. When launching the Oracle GoldenGate executables with Oracle data layer dependency, it is mandatory to go through the bundled instant client connectivity, libraries, and tools..

Microservices Architecture does not support the management of individual threads for coordinated Replicat: Microservices Architecture does not support the management of individual threads for coordinated Replicat. If you are using individual threads in Classic Architecture and are migrating to MA, you may need to remove those threads before migrations.

A new Extract needs to be created when the DB timezone is changed: You need to create new Extract if DB timezone is changed, especially in case of Oracle Cloud deployment.

4 Default Behavior Changes