INSERTUPDATES | NOINSERTUPDATES

Valid For

Replicat

Description

Use the INSERTUPDATES and NOINSERTUPDATES parameters to control whether or not Oracle GoldenGate converts update operations to insert operations. For updates to be converted to inserts, the database must log all column values either by default or by means of supplemental logging.

The parameters are table-specific. One parameter remains in effect for all subsequent MAP statements, until the other parameter is encountered.

To ensure that updates are not compressed by Extract when using INSERTUPDATES, use the NOCOMPRESSUPDATES parameter. If the database includes all columns by default, then you must use NOCOMPRESSUPDATES and NOCOMPRESSDELETES for INSERTUPDATES to work properly. If the database does not support NOCOMPRESSDELETES, you must use FETCHOPTIONS MISSINGCOLS.

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 INSERTUPDATES threads in one set of MAP statements, and specify the NOINSERTUPDATES threads in a different set of MAP statements.

Default

NOINSERTUPDATES

Syntax

INSERTUPDATES | NOINSERTUPDATES

Example

This example shows how you can apply INSERTUPDATES and NOINSERTUPDATES selectively to different MAP statements, each of which represents a different thread of a coordinated Replicat.

INSERTUPDATES
MAP sales.cust, TARGET sales.cust, THREAD (1);
MAP sales.ord, TARGET sales.ord, THREAD (2);
NOINSERTUPDATES
MAP sales.loc, TARGET sales.loc, THREAD (3);