Details of Support When Using Oracle GoldenGate with Autonomous AI Databases

Review the supported data types and limitations before replicating data or from an Oracle Autonomous AI Database instance.

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

Oracle GoldenGate Replicat Limitations for Autonomous AI Databases

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

To replicate data into an Oracle Autonomous AI Database you must use Parallel Replicat (integrated or non-integrated mode) or Integrated Replicat.

Data Type Limitations for DDL and DML Replication

See the section Non-Supported Oracle Data Types.

Also see Data Types in the Autonomous AI Database on Dedicated Exadata Infrastructure Documentation and Data Types in the Using Oracle Autonomous AI 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 AI Databases, Autonomous AI Database Serverless and Autonomous AI Database on Dedicated Exadata Infrastructure have different log retention behavior.

  • Autonomous AI 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.

  • Autonomous AI Database on Dedicated Exadata Infrastructure: When Oracle Autonomous AI Database 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.