Table-Level Identification Key Logging

As an example, the following statement specifies the table-level identification supplemental logging for table ALLINSURED.  The implies that when any column in the ALLINSURED table is changed, the entire row, except LOB, LONGs, and ADTs, of the table is placed in the redo log file.

SQL> ALTER TABLE NYDATA1.ALLINSURED ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

Table-Level User-Defined Supplemental Log Groups

In addition to table-level identification key logging, Oracle supports table level user-defined supplemental log groups. Such log groups can be conditional or unconditional. Table level logging provides better control over configuration and will help to minimize the overall additional logging data.

To create user defined unconditional log groups, the ALWAYS clause is used. For example, to create a group called allins_polno for table ALLINSURED, use the following statement:

SQL> ALTER TABLE ALLINSURED ADD SUPPLEMENTAL LOG GROUP allins_polno (POL_NO, SALES_ID) ALWAYS;

To create supplemental logging that uses user-defined conditional log groups at the table level, omit the ALWAYS clause from the ALTER TABLE statement. An example is shown next: