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 : 17-08-2017

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

  • ora-26098 : direct path context is not prepared
  • ora-23310 : object group "string"."string" is not quiesced
  • ora-21703 : cannot flush an object that is not modified
  • ora-25259 : cannot specify protocol for agent
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-13757 : "SQL Tuning Set" "string" owned by user "string" is active.
  • ora-38453 : ExpFilter index should be created in the same schema as the base table.
  • ora-31196 : XML nodes over string in size cannot be printed
  • ora-02708 : osnrntab: connect to host failed, unknown ORACLE_SID
  • ora-00237 : snapshot operation disallowed: control file newly created
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • ora-03251 : Cannot issue this command on SYSTEM tablespace
  • ora-19604 : conversation file naming phase is over
  • ora-12492 : DBLOW cannot be changed
  • ora-07671 : $IDTOASC failed translating an integrity category
  • ora-00607 : Internal error occurred while making a change to a data block
  • ora-30199 : reserved for future use
  • ora-14136 : ALTER TABLE EXCHANGE restricted by fine-grained security
  • ora-24789 : start not allowed in recursive call
  • ora-23393 : the user is already the propagator
  • ora-21613 : key does not exist
  • ora-40203 : model string does not exist
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-19960 : Internal use only
  • ora-02364 : error writing to file: string
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-01621 : cannot rename member of current log if database is open
  • ora-08275 : Environment variable unset
  • ora-16818 : Fast-Start Failover suspended
  • 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.