1. Oracle GoldenGate Classic Documentation
  2. Autonomous Database
  3. Using Oracle GoldenGate with Autonomous Database
  4. Configuring Replicat to Apply to an Autonomous Database
  5. Prerequisites for Configuring Oracle GoldenGate Replicat to an Autonomous Database
  6. Configure Oracle GoldenGate Replicat for an Autonomous Database

Configure Oracle GoldenGate Replicat for an Autonomous Database

Learn the steps to configure Oracle GoldenGate Replicat for an Autonomous Databases.

Here are the steps to complete the configuration tasks:

Note:

Instructions are based on the assumption that the source environment is already configured. Learn the steps required to configure replication into the Autonomous Database environment.

  1. For Oracle GoldenGate on-premises, make sure that Oracle GoldenGate is installed.

    Oracle GoldenGate Classic Architecture support Autonomous Database capture using Marketplace for Oracle Autonomous Database Serverless.

  2. Start GGSCI.

    ./ggsci

  3. The Autonomous Database instance has a pre-created user created for Oracle GoldenGate on-premise called ggadmin. The ggadmin user has been granted the required privileges for Replicat to work. This is the user where any objects used for Oracle GoldenGate processing will be stored, like the checkpoint table and heartbeat objects. By default, this user is locked. To unlock the ggadmin user, connect to the Oracle Autonomous Database instance as the ADMIN user using any SQL client tool. See Create Users on Autonomous Database with Database Actions.

  4. Run the ALTER USER command to unlock the ggadmin user and set the password for it. This will be used in GGSCI for any DBLOGIN operations on the Autonomous Database. It will be used in Replicat to allow Oracle GoldenGate to connect to the Autonomous Database and apply data. See Create Users on Autonomous Database with Database Actions.
    ALTER USER ggadmin IDENTIFIED BY p0$$word ACCOUNT UNLOCK;