ORA-16258: marking index unusable due to a constraint violation

Cause : A constraint violation occurred during the apply of a direct path load. The index will be marked unusable and the apply will be restarted.

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

No action necessary. See alert log for index schema and name.

update : 25-04-2017

ORA-16258 - marking index unusable due to a constraint violation
ORA-16258 - marking index unusable due to a constraint violation

  • ora-22852 : invalid PCTVERSION LOB storage option value
  • ora-26092 : only LONG or LOB types can be partial
  • ora-07391 : sftopn: fopen error, unable to open text file.
  • ora-31641 : unable to create dump file "string"
  • ora-16816 : incorrect database role
  • ora-15004 : alias "string" does not exist
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-31116 : Tablespace not specified correctly
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-09742 : sppst: error during a post.
  • ora-36914 : (XSAGDNGL50) In AGGMAP workspace object, LOAD_STATUS valueset workspace object contains both a child and it's ancestor.
  • ora-16506 : out of memory
  • ora-15073 : diskgroup string is mounted by another ASM instance
  • ora-01720 : grant option does not exist for 'string.string'
  • ora-19692 : missing creation stamp on piece string
  • ora-14254 : cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
  • ora-27147 : post/wait reset failed
  • ora-30345 : circular dimension hierarchy
  • ora-16700 : the standby database has diverged from the primary database
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-30688 : maximum program calling depth exceeded
  • ora-12718 : operation requires connection as SYS
  • ora-12039 : unable to use local rollback segment "string"
  • ora-30064 : Test support for two phase read only optimization
  • ora-15105 : missing or invalid FAILGROUP name
  • ora-01072 : cannot stop ORACLE; ORACLE not running
  • ora-01660 : tablespace 'string' is already permanent
  • ora-19111 : error during evaluation of the XQuery expression
  • ora-13778 : no new name or owner specified for "SQL Tuning Set"
  • ora-12639 : Authentication service negotiation failed
  • 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.