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 : 27-04-2017

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

  • ora-39116 : invalid trigger operation on mutating table string.string
  • ora-28139 : Maximum allowed Fine Grain Audit Policies Exceeded
  • ora-06804 : TLI Driver: could not bind an IPX address at initialization
  • ora-30115 : error when processing an environment variable
  • ora-19613 : datafile string not found in backup set
  • ora-39165 : Schema string was not found.
  • ora-06037 : NETDNT: connect failed, node unreachable
  • ora-33016 : (XSAGDNGL07) In AGGMAP workspace object, workspace object is not a valid operator or variable name.
  • ora-32819 : AQ queue string must be a normal queue
  • ora-13787 : missing SQL profile for statement object "string" for tuning task "string"
  • ora-32330 : invalid operation on online redefinition interim table "string"."string"
  • ora-06917 : CMX: error in data read (too many bytes read)
  • ora-00275 : media recovery has already been started
  • ora-16111 : log mining and apply setting up
  • ora-30026 : Undo tablespace 'string' has unexpired undo with string(sec) left, Undo_Retention=string(sec)
  • ora-25454 : error during evaluation of rule set: string.string for iterator: string
  • ora-09883 : Two Task interface: oratab file does not exist
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-00378 : buffer pools cannot be created as specified
  • ora-07496 : sppst: lm_post failed.
  • ora-01077 : background process initialization failure
  • ora-14275 : cannot reuse lower-bound partition as resulting partition
  • ora-23328 : mview base table "string"."string" differs from master table "string"."string"
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-29556 : object type has changed
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-30355 : materialized view container does not exist
  • ora-22973 : size of object identifier exceeds maximum size allowed
  • ora-30077 : illegal casting between specified datetime types
  • ora-31205 : DBMS_LDAP: PL/SQL - Invalid LDAP Auth method.
  • 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.