Prerequisites for Capturing from an Autonomous Database

Oracle Autonomous Database has a tight integration with Oracle GoldenGate. There are a number of differences when setting up Extract for an Autonomous database instance compared to a traditional Oracle Database.

Oracle Autonomous Database security has been enhanced to ensure that Extract is only able to capture changes from the specific tenant it connected to. Therefore, Downstream Integrated Extract is not supported.

Establishing Oracle GoldenGate Credentials

To capture from an Autonomous Database only the GGADMIN account is used. The GGADMIN account is created inside the database when the Autonomous Database is provisioned and already has all the necessary permissions for both Extract and Replicat processes. This account is locked. It must be unlocked before it can be used with Oracle GoldenGate. This account is the same account used for both Extracts and Replicats in the Autonomous Database.

Note:

Run the ALTER USER command to unlock the ggadmin user and set the password for it. See Creating Users with Autonomous Database with Client-Side Tools.

This ALTER USER command must be run by the admin account user for Autonomous Databases. 

ALTER USER ggadmin IDENTIFIED BY PASSWORD ACCOUNT UNLOCK;

Configure Oracle Autonomous Database for Oracle GoldenGate Extract

Prior to configuring and starting the Extract process to capture from the Autonomous Database, make sure that the following requirements are met:

  • Oracle Autonomous Database environment is provisioned and running.

  • Autonomous Database-level supplemental logging should be enabled by the ADMIN or GGADMIN.

Configuring Autonomous Database Supplemental Logging for Extract

To add minimal supplemental logging to your Autonomous Database instance, log into the instance as GGADMIN or ADMIN account and execute the following commands:
ALTER PLUGGABLE DATABASE ADD SUPPLEMENTAL LOG DATA;
To DROP Autonomous Database-level supplemental logging incase you decide to stop capturing from that database instance:
ALTER PLUGGABLE DATABASE DROP SUPPLEMENTAL
        LOG DATA;
You can verify that the Autonomous Database-level supplemental logging is configured properly by issuing this SQL statement:
SELECT MINIMAL FROM dba_supplemental_logging;
The output for this statement is:
MINIMAL
-------
YES

The MINIMAL column will be YES if supplemental logging has been correctly set for this Autonomous Database instance.