Forced logging mode

ALTER DATABASE FORCE LOGGING;

Forces the logging of all transactions and loads.

Strongly recommended for all Oracle GoldenGate use cases. FORCE LOGGING overrides any table-level NOLOGGING settings.

Minimum database-level supplemental logging

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA

Enables minimal supplemental logging to add row-chaining information to the redo log.

Required for all Oracle GoldenGate use cases

Schema-level supplemental logging, default setting

See Enabling Schema-level Supplemental Logging.

ADD SCHEMATRANDATA

Enables unconditional supplemental logging of the primary key and conditional supplemental logging of unique key(s) and foreign key(s) of all tables in a schema. All of these keys together are known as the scheduling columns.

Enables the logging for all current and future tables in the schema. If the primary key, unique key, and foreign key columns are not identical at both source and target, use ALLCOLS. Required when using DDL support.

Schema-level supplemental logging with unconditional logging for all supported columns. (See Enabling Schema-level Supplemental Logging for non-supported column types.)

ADD SCHEMATRANDATA with ALLCOLS option

Enables unconditional supplemental logging of all of the columns in a table, for all of the tables in a schema.

Used for bidirectional and active-active configurations where all column values are checked, not just the changed columns, when attempting to perform an update or delete. This takes more resources though allows for the highest level of real-time data validation and thus conflict detection.

This method should also be used if they are going to be using the HANDLECOLLISIONS parameter for initial loads.

Schema-level supplemental logging, minimal setting

ADD SCHEMATRANDATA with NOSCHEDULINGCOLS option

Enables unconditional supplemental logging of the primary key and all valid unique indexes of all tables in a schema.

Use only for nonintegrated Replicat. This is the minimum required schema-level logging.

Table-level supplemental logging with built-in support for integrated Replicat

See Enabling Table-level Supplemental Logging

ADD TRANDATA

Enables unconditional supplemental logging of the primary key and conditional supplemental logging of unique key(s) and foreign key(s) of a table. All of these keys together are known as the scheduling columns.

Required for all Oracle GoldenGate use cases unless schema-level supplemental logging is used. If the primary key, unique key, and foreign key columns are not identical at both source and target, use ALLCOLS.

Table-level supplemental logging with unconditional logging for all supported columns. (See Enabling Table-level Supplemental Logging for non-supported column types.)

ADD TRANDATA with ALLCOLS option

Enables unconditional supplemental logging of all of the columns of the table.

Used for bidirectional and active-active configurations where all column values are checked, not just the changed columns, when attempting to perform an update or delete. This takes more resources though allows for the highest level of real-time data validation and thus conflict detection.

It can also be used when the source and target primary, unique, and foreign keys are not the same or are constantly changing between source and target.

Table-level supplemental logging, minimal setting

ADD TRANDATA with NOSCHEDULINGCOLS option

Enables unconditional supplemental logging of the primary key and all valid unique indexes of a table.

Use for nonintegrated Replicat and non-parallel Replicat. This is the minimum required table-level logging.