Switching Replicat to Coordinated Mode
Valid for all database types supported by Oracle GoldenGate.
This procedure upgrades a regular Replicat configuration (non-coordinated) to a coordinated configuration. This procedure assumes you are replacing a configuration that partitions data across multiple Extract and Replicat processes with a configuration that uses one Extract and one coordinated Replicat. The coordinated Replicat replaces the need for using multiple Replicat processes. A coordinated Replicat requires only one trail, so there is no need for multiple Extract processes.
Procedure Overview
This procedure makes use of the EVENTACTIONS
parameter with a STOP
action, which enables all of the Replicat processes to stop at the same point in the trail. The EVENTACTIONS
action is triggered by a transaction that contains an INSERT
to a dummy table. The INSERT
causes each process to finish processing everything up to, and including, the event transaction and then stop cleanly. An additional event action of IGNORE
is specified for Replicat to prevent the multiple Replicat processes from attempting to insert the same record to the target. The result of this procedure is that all processes stop at the same point in the data stream: after completing the INSERT
transaction to the dummy table.
After the processes stop, you move all of the TABLE
statements to
one primary Extract group. You move all of the MAP
statements to a new
coordinated Replicat group that reads the trail associated with the retained Extract.
After all of the MAP
statements are in one parameter file, you edit
them to add the thread specifications to support a coordinated Replicat. (This can be
done ahead of time.) Then you drop the Replicat group and add it back in coordinated
mode with the same name.