ORA-16130: supplemental log information is missing from log stream

Cause : Supplemental logging is not enabled at the primary database.

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

Issue the following command to enable supplemental logging. ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS;

update : 21-07-2017
ORA-16130

ORA-16130 - supplemental log information is missing from log stream
ORA-16130 - supplemental log information is missing from log stream

  • ora-16818 : Fast-Start Failover suspended
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-01651 : unable to extend save undo segment by string for tablespace string
  • ora-38731 : Expected version string does not match string in log header.
  • ora-21602 : operation does not support the specified typecode
  • ora-40290 : model incompatible with data mining function
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-09241 : smsalo: error allocating SGA memory
  • ora-14008 : missing THAN keyword
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-06567 : invalid number of values specified
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-02218 : invalid INITIAL storage option value
  • ora-02054 : transaction string in-doubt
  • ora-31421 : change table does not exist
  • ora-32585 : duplicate specification of a supplemental log attribute
  • ora-01945 : DEFAULT ROLE[S] already specified
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-28541 : Error in HS init file on line number.
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • ora-01255 : cannot shutdown - file string in recovery manager backup
  • ora-31662 : metadata transform name can not be defaulted
  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-27503 : IPC error attempting to cancel request
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-19574 : output filename must be specified
  • ora-07401 : sptrap: cannot restore user exception handlers.
  • ora-00132 : syntax error or unresolved network name 'string'
  • ora-01275 : Operation string is not allowed if standby file management is automatic.
  • 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.