Valid For
Replicat
Description
Use the RESTARTCOLLISIONS
and NORESTARTCOLLISIONS
parameters to control whether or not Replicat applies HANDLECOLLISIONS
logic after Oracle GoldenGate has stopped because of a conflict. By default, NORESTARTCOLLISIONS
applies. However, there might be circumstances when you would want Oracle GoldenGate to apply HANDLECOLLISIONS
logic for the first transaction after startup. For example, if the server is forcibly shut down, the database might have committed the last Replicat transaction, but Oracle GoldenGate might not have received the acknowledgement. Consequently, Replicat will retry the transaction upon startup. HANDLECOLLISIONS
automatically handles the resultant errors that occur.
RESTARTCOLLISIONS
enables HANDLECOLLISIONS
functionality until the first Replicat checkpoint (transaction) is complete. You need not specify the HANDLECOLLISIONS
parameter in the parameter file. After the first checkpoint, HANDLECOLLISIONS
is automatically turned off.
See "HANDLECOLLISIONS | NOHANDLECOLLISIONS" for more information about handling collisions.
Default
NORESTARTCOLLISIONS
Syntax
RESTARTCOLLISIONS | NORESTARTCOLLISIONS