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 : 24-05-2017

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

  • ora-25103 : NOPARALLEL option can only be used with ALTER INDEX REBUILD
  • ora-30153 : An invalid File Object is passed to the OCIFile function
  • ora-40214 : duplicate setting: string
  • ora-08237 : smsget: SGA region not yet created
  • ora-31100 : XDB Locking Internal Error
  • ora-00372 : file string cannot be modified at this time
  • ora-32620 : illegal subquery within MODEL rules
  • ora-16732 : error executing dbms_logstdby.skip procedure
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-07685 : sou2os: supervisor stack set error
  • ora-02098 : error parsing index-table reference (:I)
  • ora-16605 : unable to delete template, template is in use
  • ora-24500 : invalid UTF16 mode
  • ora-32603 : invalid FREEPOOLS LOB storage option value
  • ora-38102 : Invalid column in the INSERT WHERE Clause: string
  • ora-01977 : Missing thread number
  • ora-09203 : sfofi: error opening file
  • ora-01338 : Other process is attached to LogMiner session
  • ora-32401 : materialized view log on "string"."string" does not have new values
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-13777 : invalid list of attribute names
  • ora-15097 : cannot SHUTDOWN ASM instance with connected RDBMS instance
  • ora-19955 : only one open thread is allowed to change the DBID
  • ora-12052 : cannot fast refresh materialized view string.string
  • ora-32822 : subscriber string is marked for removal
  • ora-32140 : cannot peform this operation on stream
  • ora-32060 : channel failure
  • ora-13196 : failed to compute supercell for element string.string.string
  • ora-28276 : Invalid ORACLE password attribute.
  • ora-36975 : (XSRELTBL15) You must specify a USING clause naming a relation with same level dimension as LEVELORDER valueset workspace object.
  • 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.