Release 21c (21.1.0): Initial Release May 2021

Oracle GoldenGate Microservices Architecture is available with Oracle and heterogeneous databases
Oracle GoldenGate 21c supports the following databases:

  • Oracle Database

  • DB2 z/OS

  • MySQL

  • SQL Server

All Databases
Parallel Replicat Core Infrastructure Support for Heterogeneous Databases

Parallel Replicat is supported with SQL Server, DB2 z/OS, and MySQL.

Heartbeat History Endpoints Display Historic Heartbeat and Lag Information for ER Processes
Historic and lag information for ER processes and heartbeat records is retrieved and is available from the Administration Server's Replicat Process Information page.
Oracle Database
Unified Build Support

Oracle GoldenGate uses a single, unified build for capturing from and applying to multiple major Oracle Database versions for supported operating systems by including the latest Oracle database client libraries as part of Oracle GoldenGate.

Automatic Extract of tables with supplemental logging is supported
Oracle GoldenGate provides a new auto_capture mode to capture changes for all the tables that are enabled for logical replication. You can list the tables enabled for auto-capture using the LIST TABLES AUTO_CAPTURE command option. Use the TRANLOGOPTIONS ENABLE_AUTO_CAPTURE option to set up automatic capture.

When this parameter is enabled in Extract, any table that has supplemental logging on it will be automatically captured by Extract and you don't need to add the table as a TABLE parameter. You can use the new DDL options for ALTER TABLE ... ENABLE LOGICAL REPLICATION ALL KEYS, ALTER TABLE ... ENABLE LOGICAL REPLICATION ALLOW NOVALIDATE KEYS, CREATE TABLE ... ENABLE LOGICAL REPLICATION ALL KEYS, or CREATE TABLE ... ENABLE LOGICAL REPLICATION NOVALIDATE KEYS to add supplemental logging to a table and allow Oracle GoldenGate to automatically capture it. This also requires Oracle Database 21c and higher.

Oracle native JSON datatype is supported
Oracle GoldenGate capture and apply processes now support the new native JSON datatype, which is supported by Oracle Database 21c and higher.
Automatic Conflict Detection and Resolution for Oracle Database 21c is available

This feature provides support in Oracle Database 21c and Oracle GoldenGate to enhance Automatic CDR to support:

  • Earliest timestamp resolution

  • Delete always win

  • Site priority resolution

These features can be enabled in the DBMS_GOLDENGATE.ADD_AUTO_CDR procedure.

Kerberos Authentication is supported
Oracle GoldenGate supports external authentication for database login (DBLOGIN) for Kerberos user accounts.
Oracle Cloud Infrastructure Key Management Service (OCI KMS) integration is available

Oracle GoldenGate supports integration with the OCI KMS for trail file encryption, which simplifies securing Oracle GoldenGate cloud deployments.

Autonomous Database Extract is supported
Oracle GoldenGate can now capture from the Autonomous Databases in OCI. This feature allows capturing data out of specific Autonomous environment in a secure way without allowing access to any other data in that shared environment. For additional details, see Capturing from Pluggable Databases in Using Oracle GoldenGate for Oracle Database.
Replicat Compatibility Constraint

Replicat compatibility with different trail file formats is ensured using this feature. The Replicat compatibility constraint is associated to the record (LCR) by the primary Extract to restrict certain record to apply by specific version of Replicat in Oracle GoldenGate 21c or higher releases without bumping up the trail file format version. This feature is displayed by the LogDump utility.

Large DDL (greater than 4 MB) replication is supported

DDLs that are greater than 4 MB in size will be provided replication support.

Certificate management is available from the Microservices Architecture Web UI

Server certificates and multiple client certificates can be managed from the Servicer Manager. Each deployment has a Certificate Store that holds the server, client certificates, and CA certificates, which are used when setting up a secure communication channels for a deployment.

Support for multiple client certificates for wss protocol is available

You can store multiple client certificates in the Certificate Store and explicitly specify the type of authentication mechanism for the distribution paths and target-initiated paths as part of the specification.

You can select one of the three authentication mechanisms, Credentials, Client Certificates, or OAuht2.0 (available with Oracle GoldenGate 21.3.0). If you choose the client certificate authentication mechansim, then you can chose a specific client certificate.

DB_UNIQUE_NAME with heartbeat table

DB_UNIQUE_NAME is available with the heartbeat table to allow users to uniquely identify the source of the heartbeat. DB_UNIQUE_NAME will allow better use of the heartbeat table in active-active environments, where, typically all the replicas have the same DB_NAME but identify each replica site uniquely using the DB_UNIQUE_NAME.

DB_UNIQUE_NAME with trail file header

DB_UNIQUE_NAME is added in the trail file header along with DB_NAME, which helps in troubleshooting replication in active-active environments, where mostly all replicas have the same DB_NAME but identify each replica site uniquely using the DB_UNIQUE_NAME.

Oracle GoldenGate Upgrade Simplification

The process to upgrade to Oracle GoldenGate 21c has been further simplified. There are fewer steps necessary for the administrator to upgrade to the latest Oracle GoldenGate release. This includes automatic repositioning of Replicat after a trail file format upgrade.

Partition Name Filtering

The Partition Filtering option filters explicitly on the partition name of tables. Data can be filtered based on source partition names in Extract, Pump, Distribution Service, and Replicat.

Bounded Recovery Checkpoint Performance

The Bounded Recovery (BR) Checkpoint has been enhanced to allow Extract to continue mining the redo log and generate trail files during the BR checkpoint, which decreases the BR intervals and improves Extract restart times.

Active Data Guard (ADG) Redirection

If ADG is configured in a cascaded mode to transport redo logs to a downstream database, Oracle GoldenGate can connect to ADG as a source database for the REGISTER command instead of connecting to the database where redo is originated. There is no source database connection needed for registering Extract.

New Replicat parameter INCLUDETAG

Oracle GoldenGate for Oracle now supports INCLUDETAG in addition to the existing EXCLUDETAG parameter to allow more flexibility in configuring multi-way replication topologies.

DB2 z/OS
Capture from temporal tables is supported
Capture from temporal tables is supported with DB2 z/OS.
ECSA Storage is reduced when capturing from DB2 z/OS

ECSA storage requirements is reduced by using 64-bit common storage for storing log read buffers .

EOF option is supported for ADD/ALTER EXTRACT

The EOF option is supported to allow Extract to support various starting positions.

MySQL
DDL replication with remote capture
Oracle GoldenGate supports DDL replication with remote capture from MySQL 8.0 onwards.
Capture DDL metadata from BINLOG

Supports capturing DDL and metadata directly from MySQL BINLOG for MySQL version 8.0 and higher.

JSON Datatype Support

MySQL capture and delivery of JSON data is now supported.

SQL Server
Support SQL Server 2019 Standard and Enterprise

Capture and Delivery for SQL Server 2019 Enterprise and Standard Editions is supported.

Support Azure SQL Server Database Managed Instance

Capture and delivery for Azure SQL Server database managed instance is supported.