1. Oracle GoldenGate Classic Documentation
  2. Administer
  3. Performing Administrative Operations
  4. Switching Replicat to Coordinated Mode
  5. Performing the Switch to Coordinated Replicat

Performing the Switch to Coordinated Replicat

Note:

Do not create the Replicat group until prompted by these instructions.

  1. Back up the current parameter files of all of the Extract groups, data pumps, and Replicat groups. You will be editing them.
  2. Create a working directory outside the Oracle GoldenGate directory. You will use this directory to create and stage new versions of the parameter files. If needed, you can create a working directory on the source and target systems.
  3. In the working directory, create a parameter file for a coordinated Replicat. Copy the MAP parameters from the active parameter files of all of the Replicat groups to this parameter file, and then add the thread specifications and any other parameters that support your required coordinated Replicat configuration
  4. If using multiple primary Extract groups, select one to keep, and then save a copy of its current parameter file to the working directory.
  5. Copy all of the TABLE statements from the other Extract groups to the new parameter file of the primary Extract that you are keeping.
  6. In the working directory, save a copy of the parameter file of the data pump that is linked to the primary Extract that you are keeping.
  7. Copy all of the TABLE statements from the other data pumps to the copied parameter file of the kept data pump.
  8. In the source database, create a simple dummy table on which a simple INSERT statement can be performed. For this procedure, the name schema.event is used.
  9. Create the same table on the target system, to avoid the need for additional configuration parameters.
  10. Edit the active parameter files (not the copies) of all primary and data-pump Extract groups to add the following EVENTACTIONS parameter to each one.
    TABLE schema.event, EVENTACTIONS(STOP);
  11. Edit the active parameter files (not the copies) of all of the Replicat groups to add the following EVENTACTIONS parameter to each one.
    MAP schema.event, TARGET schema.event, EVENTACTIONS(IGNORE, STOP);
  12. Stop the Oracle GoldenGate processes gracefully in the following order:

    • Stop all Replicat processes.

    • Stop all data pumps.

    • Stop all Extract processes.

  13. Restart the Oracle GoldenGate processes in the following order so that the EVENTACTIONS parameters take effect:

    • Start all Extract processes.

    • Start all data pumps.

    • Start all Replicat processes.

  14. On the source system, issue a transaction on the schema.event table that contains one INSERT statement. Make certain to commit the transaction.
  15. In GGSCI, issue the STATUS command for all of the primary Extract and data pump processes on the source system, and issue the same command for all of the Replicat processes on the target system, until the commands show that all of the processes are STOPPED.
    STATUS EXTRACT *
STATUS REPLICAT *
  16. Replace the active parameter files of the primary Extract and data pump that you kept with the new parameter files from the working directory.
  17. Delete the unneeded Extract and data pump groups and their parameter files.
  18. Log into the target database by using the DBLOGIN command.
  19. Delete all of the Replicat groups and their active parameter files.
  20. Copy or move the new coordinated Replicat parameter file from the working directory to the Oracle GoldenGate directory.
  21. In GGSCI, issue the INFO EXTRACT command for the data pump and make note of its write checkpoint position in the output (remote) trail.
    INFO EXTRACT pump, DETAIL
  22. Add a new coordinated Replicat group with the following parameters.
    ADD REPLICAT group, EXTTRAIL trail, EXTSEQNO sequence_number, EXTRBA rba, COORDINATED MAXTHREADS number

    Where:

    • group is the name of the coordinated Replicat group. The name must match that of the new parameter file created for this group.

    • EXTTRAIL trail is the name of the trail that the data pump writes to.

    • EXTSEQNO sequence_number is the sequence number of the trail as shown in the write checkpoint returned by the INFO EXTRACT that you issued for the data pump.

    • EXTRBA rba is the relative byte address in the trail as shown in the write checkpoint returned by INFO EXTRACT. Together, these position Replicat to resume processing at the correct point in the trial.

    • MAXTHREADS number specifies the maximum number of threads allowed for this group. This value should be appropriate for the number of threads that are specified in the parameter file.

  23. Start the primary Extract group.
  24. Start the data pump group.
  25. Start the coordinated Replicat group.