Enabling Table-Level Supplemental Logging
Enabling Supplemental logging is a process in which Oracle GoldenGate sets source database table level logging to support change data capture of source DML operations, and depending on the level of logging, to include additional, unchanged columns which would be needed in cases such as bi-directional replication with conflict detection and resolution configured.
There are four levels of table level logging in PostgreSQL, which equate to the
REPLICA IDENTITY
setting of a table, and those include
NOTHING
, USING INDEX
, DEFAULT
, and
FULL
.
Oracle GoldenGate requires FULL
logging for use cases that
require uncompressed trail records and Conflict Detection and Resolution, but in cases where
tables have a Primary Key or Unique Index whose changes are being replicated in a simple
uni-directional configuration or where full before-images or uncompressed records are not
needed, then the DEFAULT
level is acceptable. NOTHING
and
USING INDEX
logging levels are not supported by Oracle GoldenGate and
cannot be set with ADD TRANDATA
.
ADD TRANDATA
from the
Admin
Client.DBLOGIN SOURCEDB dsn_name USERIDALIAS alias_name
ADD TRANDATA schema.tablename ALLCOLS
Note:
For tables that have a primary key or unique index, theALLCOLS
option is
required in order to set FULL
logging for the table, otherwise
DEFAULT
logging is set.
FULL
logging is always set for tables without a primary key or unique index,
regardless of whether ALLCOLS
is specified or not.
INFO TRANDATA schema.tablename