1. Oracle GoldenGate Classic Documentation
  2. Administer
  3. Performing Administrative Operations
  4. Administering a Coordinated Replicat Configuration
  5. Recovering Replicat After an Unplanned Re-partitioning
  6. Using the Auto-Saved Parameter File

Using the Auto-Saved Parameter File

A copy of the original parameter file is saved whenever the parameter file is edited before shutting down Replicat cleanly. You can revert to this parameter file and then resynchronize the threads so that they all catch up to the thread that had the most recent checkpoint position. Once the threads are synchronized, you can switch to the new parameter file and then start Replicat.

  1. Save the new parameter file to a different name, and then rename the saved original parameter file to the correct name (same as the group name). The saved parameter file has a .backup suffix and is stored in the dirprm subdirectory of the Oracle GoldenGate installation directory.
  2. Issue the following command to synchronize the Replicat threads to the maximum checkpoint position. This command automatically starts Replicat and executes the threads until they reach the maximum checkpoint position.
    SYNCHRONIZE REPLICAT group
  3. Issue the STATUS REPLICAT command until it shows that Replicat stopped cleanly.
    STATUS REPLICAT group
  4. Save the original parameter file to a different name, and then rename the new parameter file to the group name.
  5. Start Replicat.
    START REPLICAT group