...
Supplemental logging is not the default behaviour behavior of the oracle Oracle database. It has to be enabled manually after the database is created. It can be enabled at two levels
...
- For all columns
- For primary key columns
- For unique columns
- For foreign key columns
Note |
---|
Dbvisit Replicate automatically turns on supplemental logging and sets the minimal logging level based on the replication requirement. No manual supplemental logging steps are required. |
...
No Format | ||
---|---|---|
| ||
SQL> alter database add supplemental log data; |
...
If DDL is enabled, then the following is run
No Format | ||
---|---|---|
| ||
SQL> alter database add supplemental log data (primary key) columns; |
...
For each table to be replicated the following SQL is run
No Format | ||
---|---|---|
| ||
SQL> alter table '||owner||'.'||table_name||' add supplemental log data (primary key) columns; |
The supplemental log groups created by Dbvisit Replicate start with a G and then a random hex string: G575B4B0CC2E511E2A20CB8ADB3813
...
No Format | ||
---|---|---|
| ||
SQL> SELECT supplemental_log_data_min MIN, supplemental_log_data_pk PK, supplemental_log_data_ui UI, supplemental_log_data_fk FK, supplemental_log_data_all "ALL" FROM v$database; |
Modifying supplemental log
...
behavior
Please see the variables _ADD_SUPLOG and _MINE_KEY_IMAGE_PREFER_SUPLOG in Internal Variables on the default supplemental log behavior and how to modify this.
...