ORA-16806: supplemental logging is not turned on

Cause : Supplemental logging was not turned on while there is a logical standby database in the configuration. This could happen either on the primary or on the logical standby database that is being switched over to be the primary database.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Check Data Guard broker log for more details. Issue the ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.

update : 26-06-2017

ORA-16806 - supplemental logging is not turned on
ORA-16806 - supplemental logging is not turned on

  • ora-00446 : background process started when not expected
  • ora-09820 : Conversion of class string to numeric representation failed.
  • ora-16056 : backup control file archival requires proper syntax
  • ora-03243 : destination dba overlaps with existing control information
  • ora-01616 : instance string (thread string) is open - cannot disable
  • ora-32620 : illegal subquery within MODEL rules
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-16638 : could not get the instance status
  • ora-16232 : adding Logical Standby skip entry for table string.string
  • ora-08450 : invalid specification of CR in picture mask
  • ora-23343 : no match for specified conflict resolution information
  • ora-01540 : tablespace 'string' is not offline
  • ora-25508 : database is not mounted
  • ora-26664 : cannot create STREAMS process string
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-01600 : at most one "string" in clause "string" of string
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-02205 : only SELECT and ALTER privileges are valid for sequences
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-00445 : background process "string" did not start after string seconds
  • ora-09330 : Session terminated internally by Oracle or by an Oracle DBA
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-25958 : join index where clause predicate may only contain column references
  • ora-24021 : queue table definition not imported for string.string
  • ora-23424 : materialized view "string"."string" at string not registered
  • ora-19916 : %s
  • ora-30393 : a query block in the statement did not rewrite
  • ora-28654 : table and partition not overflow compatible
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.