INSERTDELETES | NOINSERTDELETES
Valid For
Replicat
Description
Use the INSERTDELETES
and NOINSERTDELETES
parameters to control whether or not Oracle GoldenGate converts source delete operations to insert operations on the target database. The parameters are table-specific. One parameter remains in effect for all subsequent MAP
statements, until the other parameter is encountered.
When using INSERTDELETES
, use the NOCOMPRESSDELETES
parameter so that Extract does not compress deletes.
Because you can selectively enable or disable these parameters between MAP
statements, you can enable or disable them for different threads of a coordinated Replicat. Specify the INSERTDELETES
threads in one set of MAP
statements, and specify the NOINSERTDELETES
threads in a different set of MAP
statements.
Default
NOINSERTDELETES
Syntax
INSERTDELETES | NOINSERTDELETES
Example
This example shows how you can apply INSERTDELETES
and NOINSERTDELETES
selectively to different MAP
statements, each of which represents a different thread of a coordinated Replicat.
NOINSERTDELETES MAP sales.loc, TARGET sales.loc, THREAD (3); INSERTDELETES MAP sales.cust, TARGET sales.cust, THREAD (1); MAP sales.ord, TARGET sales.ord, THREAD (2);
Parent topic: Oracle GoldenGate Parameters