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

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

  • ora-30386 : invalid SQL statement for DECLARE_REWRITE_EQUIVALENCE
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-14017 : partition bound list contains too many elements
  • ora-27148 : spawn wait error
  • ora-28503 : bind value cannot be translated into SQL text for non-Oracle system
  • ora-14185 : incorrect physical attribute specified for this index partition
  • ora-38442 : The ADT "string" is not in a valid state.
  • ora-36652 : (XSDUNION11) workspace object is not a string type dimension.
  • ora-02879 : sou2o: Could not gain access to protected memory
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-01151 : use media recovery to recover block, restore backup if needed
  • ora-06951 : Operating system call error
  • ora-00154 : protocol error in transaction monitor
  • ora-25140 : %s space policy cannot be specified for the string extent management
  • ora-24773 : invalid transaction type flags
  • ora-00490 : PSP process terminated with error
  • ora-13159 : Oracle table string already exists
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-12819 : missing options in PARALLEL clause
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-12564 : TNS:connection refused
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-29352 : event 'string' is not an internal event
  • ora-27122 : unable to protect memory
  • ora-12807 : process queue could not receive parallel query message
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-28184 : global user cannot have proxy permissions managed in the directory
  • ora-24311 : memory initialization failed
  • ora-00025 : failed to allocate string
  • ora-09240 : smpalo: error allocating PGA memory
  • 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.