Effects of ALTER TABLE ... ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS (supplemental_id_key_clause) (Doc ID 2067514.1)

Last updated on JUNE 11, 2024

Applies to:

Oracle GoldenGate - Version 11.1.1.0.0 to 12.1.3.0.0 [Release 11.1.1 to 12.1]
Oracle Database - Enterprise Edition - Version 8.1.7.4 to 12.1.0.2 [Release 8.1.7 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Purpose

The Oracle documentation for the ALTER TABLE ... ADD SUPPLEMENTAL LOG ... states the following:

supplemental_id_key_clause

Use this clause to specify that all or a combination of the primary key, unique key, and foreign key columns should be supplementally logged.

and:

If you specify ALL COLUMNS, then the database includes in the redo log all the fixed-length maximum size columns of that row. Such a redo log is a system-generated unconditional log group.

where it has the following syntax:

DATA
( { ALL | PRIMARY KEY | UNIQUE | FOREIGN KEY }
[, { ALL | PRIMARY KEY | UNIQUE | FOREIGN KEY } ]...
)
COLUMNS

However, the DATA (ALL) COLUMNS option may be confusing. This is because it is included in the "...key_clause", implying it applies to KEY columns only, whereas it actually means all the columns in the table.

So, the purpose of this document is to show the effects of the Supplemental Logging DATA (ALL) COLUMNS option, including the Trail file records extracted by GoldenGate.