Switching Replicat from Non-Integrated Mode to Integrated Mode

Valid for Oracle only.

For more information about Replicat modes for an Oracle database, see Types of Replicat.

This procedure switches an existing Replicat group from non-integrated to integrated mode.

Note: Do not configure the switch between Replicat modes to occur immediately after Extract recovers from a failure or is repositioned to a different location in the transaction log.

  1. Back up the Oracle GoldenGate working directories.

  2. While the Oracle GoldenGate processes continue to run in their current configuration, so that they keep up with current change activity, copy the Replicat parameter file to a new name.

  3. Grant the appropriate role to the Replicat user and perform the required configuration steps to support your business applications in integrated Replicat mode.

  4. Run the command line (Admin Client).

  5. Stop Replicat.

    STOP REPLICAT *group*

  6. Log into the target database from the Admin Client.

    DBLOGIN USERIDALIAS *alias*

    Where: alias is the alias of a user in the credential store who has the required user roles when using Oracle GoldenGate 26ai with Oracle AI Database 26ai and the privileges granted through Oracle dbms_goldengate_auth.grant_admin_privilege procedure when using Oracle GoldenGate 21c . See Grant User Privileges for Oracle AI Database 26ai and Higher and Grant User Privileges for Oracle Database 21c and Lower to know more.

  7. Alter Replicat to integrated mode.

    ALTER REPLICAT *group*, INTEGRATED

  8. Replace the old parameter file with the new one, keeping the same name.

  9. Start Replicat.

    START REPLICAT *group*

  10. Verify that Replicat is in integrated mode.

    INFO REPLICAT *group*

When you start Replicat in integrated mode for the first time, the START command registers the Replicat group with the database and starts an inbound server to which Replicat attaches. When you convert a Replicat group to integrated mode, the use of the Oracle GoldenGate checkpoint table is discontinued and recovery information is maintained internally by the inbound server and by the checkpoint file going forward. You can retain the checkpoint table in the event that you decide to switch back to non-integrated mode.