COMPRESSUPDATES | NOCOMPRESSUPDATES
Valid For
Extract
Description
Use the COMPRESSUPDATES
and NOCOMPRESSUPDATES
parameters for Extract to control the way columns are written to the trail record for UPDATE
operations.
COMPRESSUPDATES
, the default, causes Extract to write only the primary key and the changed columns of a row to the trail for update operations. This provides enough information to update the correct target record (unless conflict resolution is required), while restricting the amount of data that must be processed.
Additionally, if a substitute key is defined with the KEYCOLS
option of the TABLE
parameter, those columns are written to the trail, whether or not a primary or unique key is defined. See "KEYCOLS (columns)" for more information.
NOCOMPRESSUPDATES
sends all of the columns to the trail. This becomes the default when a table definition does not include a primary key or unique index. NOCOMPRESSUPDATES
also is required when using the Conflict Detection and Resolution (CDR) feature for a DB2 database on any of the platforms that are supported by Oracle GoldenGate. See Administering Oracle GoldenGate for more information about CDR.
COMPRESSUPDATES
and NOCOMPRESSUPDATES
apply globally for all TABLE
statements in a parameter file.
These parameters support the following databases:
- DB2 LUW
- DB2 z/OS
- DB2 for i
- MySQL
- SQL Server
- PostgreSQL
For Oracle, refer to the LOGALLSUPCOLS
parameter.
Default
COMPRESSUPDATES
Syntax
COMPRESSUPDATES | NOCOMPRESSUPDATES
For PostgreSQL, if you enable NOCOMPRESSUPDATES
then the before
image of the LOB
column will not be written into the trail.