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

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

  • ora-02443 : Cannot drop constraint - nonexistent constraint
  • ora-12422 : max policies exceeded
  • ora-12900 : must specify a default temporary tablespace for a locally managed database
  • ora-00079 : variable string not found
  • ora-39773 : parse of metadata stream failed
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-06310 : IPA: Environment variable(s) not set
  • ora-39018 : master process received invalid message number string
  • ora-36863 : (XSTFRC03) The OLAPRC_TABLE function encountered an error while parsing the COLUMNMAP.
  • ora-31221 : DBMS_LDAP: PL/SQL - Invalid LDAP SSL wallet passwd.
  • ora-07446 : sdnfy: bad value 'string' for parameter string.
  • ora-39084 : cannot detach job string for user string
  • ora-29906 : indextype string.string does not exist
  • ora-23619 : non-Oracle system error: string
  • ora-39047 : Jobs of type string cannot use multiple execution streams.
  • ora-28279 : Error reading ldap_directory_access init parameter.
  • ora-08341 : On nCUBE, this command can only be executed from instance 1.
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-06300 : IPA: Disconnect failure
  • ora-08318 : sllfsk: Error reading file
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-00604 : error occurred at recursive SQL level string
  • ora-00364 : cannot write header to new log member
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-31480 : staging database and source database cannot be the same
  • ora-28177 : incorrect Kerberos ticket version
  • ora-28025 : missing or null external name
  • ora-01648 : log string is the current log of disabled instance string (thread string)
  • ora-28347 : encryption properties mismatch
  • ora-24339 : cannot set server group name after connecting to server
  • 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.