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 : 19-08-2017

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

  • ora-01521 : error in adding data files
  • ora-00344 : unable to re-create online log 'string'
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-01019 : unable to allocate memory in the user side
  • ora-38475 : The attribute set and the associated ADT are out of sync.
  • ora-32022 : parameter value longer than string characters
  • ora-00311 : cannot read header from archived log
  • ora-31084 : error while creating table "string"."string" for element "string"
  • ora-29259 : end-of-input reached
  • ora-02338 : missing or invalid column constraint specification
  • ora-07845 : sllfcl: LIB$FREE_VM failue
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-19580 : %s conversation not active
  • ora-12069 : invalid object for offline instantiation
  • ora-00260 : cannot find online log sequence string for thread string
  • ora-16776 : health check of the redo transport service failed
  • ora-31087 : insufficient privileges to delete schema "string"
  • ora-22604 : TDS handle already generated
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-24016 : cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
  • ora-01413 : illegal value in packed decimal number buffer
  • ora-28037 : Cannot Get Session Key for RACF Authentication
  • ora-30088 : datetime/interval precision is out of range
  • ora-13127 : failed to generate target partition
  • ora-13034 : Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
  • ora-30728 : maximum number of columns exceeded
  • ora-12089 : cannot online redefine table "string"."string" with no primary key
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-38497 : Expression Filter index does not exist
  • 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.