Details of Support When Using Oracle GoldenGate with Autonomous Databases

Review the supported data types and limitations before replicating data to the Oracle Autonomous Database instance.

Oracle GoldenGate is supported for any type of Oracle Autonomous Database.

Details of Support for coexistence of Oracle GoldenGate with Transient Logical Rolling Upgrades

Coexistence of Oracle GoldenGate Extract and Replicat processes with Transient Logical Rolling Upgrades is supported.

Limitations of Extract and Replicat during Transient Logical Rolling Upgrades

Creation of new Extracts/Replicats are not supported during rolling upgrade.
Existing Extracts/Replicats will continue to capture or apply changes. However, there are restrictions on modifying the Extracts/Replicats to points before and after a rolling upgrade. You cannot alter Extract to a point before rolling upgrade after switching to the new primary.

Oracle GoldenGate Replicat Limitations for Autonomous Databases

These are the limitations of Oracle GoldenGate when replicating to or from the Oracle Autonomous Database.

Supported Replicats

The following combinations of Replicats are supported in different modes when using Oracle GoldenGate with Oracle Autonomous Database:

Parallel Replicat in integrated mode is supported for Oracle Autonomous Database Serverless.
Classic and coordinated Replicats in integrated mode are not supported for Oracle Autonomous Database.
Classic, coordinated, and parallel Replicats in non-integrated mode are supported for Oracle Autonomous Database.

Data Type Limitations for DDL and DML Replication

See the section Non-Supported Oracle Data Types.

Also see Data Types in the Autonomous Database on Dedicated Exadata Infrastructure Documentation and Data Types in the Using Oracle Autonomous Database Serverless guide.

DDL replication is supported depending on the restrictions in the Autonomous Databases.

Details of Support for Archived Log Retention

The two types of Autonomous Databases, Oracle Autonomous Database Serverless and Oracle Autonomous Database on Dedicated Exadata Infrastructure have different log retention behavior.

Oracle Autonomous Database Serverless: Archived log files are kept in Fast Recovery Area (FRA) for up to 48 hours. After that, it is purged and the archived log files are moved to NFS mount storage, which is accessible by logminer. Three copies are created. The logminer should be able to access any of the copies. This is transparent to Oracle GoldenGate Extract. After it reaches 7 days, the NFS mounted copy is permanently removed. The Extract abends with the archived log unavailable error if the required archived log file is older than 7 days.
Oracle Autonomous Database on Dedicated Exadata Infrastructure: When Oracle Autonomous Data Guard or Oracle GoldenGate is enabled, archived log files are kept in Fast Recovery Area (FRA) for up to 7 days. After that, the files are purged. There is no NFS mount location available for logminer to access archived log files that are older than 7 days. The Extract abends with the archived log unavailable error if the required archived log file is older than 7 days.

Note:
If the database instance is closed for more than 15 minutes, then the retention time is set back to 3 days. This implies that retention of archived log files is confirmed only for 3 days, regardless of whether the database instance is closed. The files are retained for 7 days only if the database instance is not closed.