New Feature

MajorVersion

Support DDL in an active-active bi-directional configuration. A new UPDATEMETADATA option of the DDLOPTIONS parameter notifies Replicat 

11.1

A new COMPLETEARCHIVELOGONLY option was added to TRANLOGOPTIONS to control when Extract starts processing an archived log: whether it starts immediately when the log becomes available or waits for the log to be written to disk first. 

11.1

Oracle GoldenGate now supports direct-load INSERTs. 

11.1

LOB support was enhanced so that for Oracle versions 10g and later, all LOBs are captured from the redo log, whether stored in-row or out-of-row. 

11.1

A new SUPPRESSTRIGGERS option was added to DBOPTIONS to prevent triggers from firing on target objects that are configured for replication with Oracle GoldenGate. 

11.1

A new DEFERREFCONST option was added to DBOPTIONS to delay the checking and enforcement of referential integrity constraints on the target tables until the Replicat transaction commits

11.1

A new Bounded Recovery feature was added that guarantees an efficient recovery after Extract stops for any reason, planned or unplanned, no matter how many open (uncommitted) transactions there were at the time that Extract stopped, nor how old they were. Bounded Recovery sets an upper boundary for the maximum amount of time that it would take for Extract to recover to the point where it stopped and then resume normal processing. A new parameter named BR was added to support this feature.

11.1

A new DBLOGREADER option was added to TRANLOGOPTIONS to enable Extract to use a newer API for capturing from an Oracle ASM instance. 

11.1

A new OUTPUTFILEUMASK parameter for GLOBALS was added to specify an octal umask that will be used by GoldenGate processes to create trail files and discard files. 

11.1

When Extract is running locally to an ASM instance, you can improve its performance in Oracle RAC by creating a bequeathed (BEQ) connection to the ASM instance instead of using TCP. 

11.1

Oracle Transparent Data Encryption (TDE) at the column and tablespace level are now supported. To support these features, a new dbms_internal_cklm.plb package is installed in the Oracle GoldenGate installation directory, and a new DECRYPTPASSWORD option was added to the DBOPTIONS parameter.

11.1

Extract can now be used in integrated capture mode with an Oracle database. Extract integrates with an Oracle database log mining server to receive change data from that server in the form of logical change records (LCR). 

11.2

Extract can be configured to capture from a local or downstream mining database. Because integrated capture is fully integrated with the database, no additional setup is required to work with Oracle RAC, ASM, and TDE. 

11.2

classic capture mode. 
Extract can still be configured to capture directly from the redo logs for any supported Oracle version. This configuration is now called classic capture mode. 

11.2

The checkpoint table has been upgraded to contain the SCN (the column name LOG_CMPLT_CSN, ) is of the last completed transaction from that replicat. 

11.2

Extract can now run on a snapshot standby database in integrated upstream mode, integrated downstream mode and in classic mode

11.2

Two new TRANLOGOPTIONS parameters were introduced: MINEFROMSNAPSHOTSTBY enables snapshot standby support NOMINEFROMSNAPSHOTSTBY disables snapshot standby support (default)

11.2

GoldenGate now supports Advanced Encryption Security (AES) in commands and parameters to support the encryption of passwords, trails, and data transfer across TCP/IP. BLOWFISH encryption is still available but recommended only for backward compatibility. 

11.2

Shared Integrated Extract - Extract for Oracle now supports multiple extracts using a shared LogMiner dictionary with the introduction of the SHARE option for REGISTER EXTRACT. Use of this option returns to an existing LogMiner data dictionary build with a specified SCN creating a clone. This allows for faster creation captures by leveraging existing dictionary builds.

12.1

Active Data Guard (ADG) - A new processing option (TRANLOGOPTIONS MINEFROMACTIVEDG) is introduced allowing you to configure Classic Extract to mine online redo logs shipped to the Oracle Active Data Guard standby system allowing real-time replication directly from ADG hosts. Oracle GoldenGate connects to the standby database to get metadata and other required data as needed.

12.1

Installation from Oracle Universal Installer - Oracle GoldenGate can now be installed using the Oracle Universal Installer (OUI). OUI is a graphical Java application. The required Java Runtime Environment (JRS) is automatically installed with OUI. The host platform must be Java-enabled. If this is the first time you are installing an Oracle product with OUI, you will be prompted to create the Oracle central inventory, which also creates a subdirectory for Oracle GoldenGate to contain inventory information. 

12.1

Integrated Replicat - Replicat for Oracle can now operate in integrated mode for improved scalability within Oracle target environments. In integrated mode, the Replicat process leverages the apply processing functionality that is available within the Oracle database. Integrated Replicat handles referential integrity and data description language (DDL) operations to ensure that these operations are done in the correct order, so that the administrator does not need to worry about things like parent-child relationships or DDL that would involve multiple tables or structure changes within a single table.

12.1

Capture and apply to multitenant container database - Oracle GoldenGate now supports the capture from, and delivery to, Oracle multitenant container databases (CDB). 

12.1

Coordinated Replicat - Replicat now can run in coordinated mode to provides improved scalability on all platforms. Coordinated Replicat is a multithreaded process that applies transactions in parallel instead of serially. Each thread handles all the filtering, mapping, conversion, SQL construction, and error handling for its assigned workload. A coordinator thread coordinates transactions across threads to account for dependencies. This enhancement simplifies the administration of Oracle GoldenGate over the use of multiple single-threaded Replicats, and it will reduce maintenance overhead of the product

12.1

Security enhancements - The following enhanced security protection was added to secure database passwords and user IDs, and the data in the trails and across TCP/IP.
                                                    Credential store: You can use a credential store to secure database user IDs and their encrypted passwords and associate them with an alias. It is the alias, not the actual user ID or password, that is specified in a command or parameter file. This feature eliminates the need to supply an encrypted password or encryption key as command or parameter input. All commands and parameters that take a database login as input have the option to specify an alias rather than an actual user ID and password. The credential store is implemented as an autologin wallet within the Oracle Credential Store Framework (CSF).
                                                  Wallet and master key: You can encrypt data in trail files and across TCP/IP by using a master-key wallet and storing one or more versions of a master key within this wallet. Oracle GoldenGate uses an auto-login wallet that does not require human intervention to supply the necessary passwords. Each time Oracle GoldenGate creates a trail file, it generates a new encryption key automatically. This encryption key encrypts the trail contents, while the master key encrypts the encryption key. To encrypt data across the network, Oracle GoldenGate generates a session key using a cryptographic function based on the master key. 

12.1

Automatic discard file creation - By default, Oracle GoldenGate processes now generate a discard file with default values whenever a process is started with the START command through GGSCI. 

12.1

ADD SCHEMATRANDATA and ADD TRANDATA have been enhanced to support integrated Replicat for Oracle. By default, these commands now enable the unconditional logging of the primary key and the conditional supplemental logging of all unique key(s) and foreign key(s) of a table. These are known as the scheduling columns, which must be available to integrated Replicat to compute dependencies. A new NOSCHEDULINGCOLS option disables the logging of scheduling columns. A new ALLCOLS option enables the unconditional logging of all of the key and non-key columns of a table.

12.1

With Oracle GoldenGate the metadata associated with each table in the replication process no longer requires the use of the SOURCEDEFS and ASSUMETARGETDEFS parameters. You can now configure replication without the need to define either of these parameters.

12.2

You can now replicate table with different column ordering without the need of SOURCEDEFS.

12.2

End to End Replication Lag : A new built-in feature that provides end-to-end replication lag views has been added.
Unidirectional lag from source to target.
Automatically calculates replication flows for all replication topologies.
Bidirectional lag when you setup in an Active-Active replication that provides both incoming and outgoing lag.
The new Oracle GoldenGate Software Command Interface (GGSCI) command, ADD HEARTBEATTABLE, enables this feature. There is no need to update the parameter files of the replication processes to enable heartbeats.
The new GG_LAG Database View allows you to view the end-to-end lag information.
  

12.2

Get detailed help on a parameter using the INFO PARAM command, which gives you in-depth detail about the parameter and where it can be used

12.2

Use the new checkprm utility to validate your parameter files. You can use checkprm to ensure the validity of your parameter files before you deploy the replication to avoid syntax errors.

12.2

Performance Toolkit Monitor
The Performance Toolkit Monitor is introduced and provides new metrics for diagnostics and tuning 

12.2

XAG Integration
Oracle GoldenGate can be configured to be more aware of Oracle Grid Infrastructure Bundled Agents (XAG) to provide a high availability environment in a cluster configuration using the XAGENABLE parameter in the GLOBALS file. 

12.2

Instantiation SCN Support
Simplified the online migration with the integration with Oracle data pump. It will retain the SCN for each table and manage the point of apply for each table to better the instantiation process.

12.2

Fetch from Oracle Active Data Guard Support
Integrated Extract now has the capability to fetch data from an Oracle Active Data Guard (ADG) Standby database eliminating any impact on the source database after Extract has reached a steady state.

12.2

The NOSUPPRESSTRIGGERS option in DBOPTIONS supports both Integrated Replicat and Classic Replicat.

12.2

Microservices Architecture
All APIs are accessible and available under standard Oracle GoldenGate Licensing, except for the APIs associated with the Performance Metric Service. To access the Performance Metric Service APIs, it requires additional licensing through Oracle GoldenGate Management Pack or Oracle GoldenGate Foundation Suite.

12.3

Procedural Replication
Integrated Replicat has been enhanced to allow you to replicate certain Oracle-supplied PL/SQL procedures that cannot be replicated as DML or DDL. This requires that the source and target databases are Oracle Database 12c Release 2 (12.2) and later.

12.3

Automatic Conflict Detection and Resolution
You can configure and manage Oracle GoldenGate to automate conflict detection and resolution when it is configured in Oracle Database 12c Release 2 (12.2) and later.

12.3

Replication of In-Database Archival
Replication for tables with row archival enabled is supported for Oracle Database 18c onward. The trail format must be 12.3 or higher

18.1

The Classic Extract (capture) is deprecated as of Oracle GoldenGate 18c (18.1.0). This means that there will be no further enhancements to the Classic Capture (Extract) process.

18.1

JDK Version Requirement with OUI and OPatch
The Oracle Universal Installer (OUI) that is used to install Oracle GoldenGate may be updated separately from the Oracle GoldenGate product. 

19.1

New HEARTBEATTABLE Options
This feature allows installing the Oracle GoldenGate Heartbeat implementation for a database used as a target only, and does not enable features that would be necessary for a source database implementation of the Heartbeat table.

19.1

Microservices implementation requires stronger passwords
The passwords for users in Microservices implementation require stronger passwords, with a capital letter, a number, and a special character.

19.1

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.

19.1

Enhanced the Heartbeat Table to include details for restarting Extract

19.1