ORA-16806
Supplemental logging is not turned on.
Cause
Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to become the primary database.
Action
Check the Oracle Data Guard broker log file for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS statement to add supplemental logging.
ORA-16806
supplemental logging is not turned on
Cause
Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to become the primary database.
Action
Check the Oracle Data Guard broker log file for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.
ORA-16806
supplemental logging is not turned on
Cause
Supplemental logging was not turned on while there was a logical standby database in the configuration. This could happen either on the primary database or on the logical standby database that was being switched over to become the primary database.
Action
Check the Oracle Data Guard broker log file for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.
