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 : 29-06-2017
ORA-16258

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

  • ora-16755 : failed to set initialization parameter
  • ora-07407 : slbtpd: invalid exponent.
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-13406 : null or invalid GeoRaster object for output
  • ora-00127 : dispatcher string does not exist
  • ora-38463 : invalid XML Tag list
  • ora-31434 : purge is currently running
  • ora-24807 : LOB form mismatch
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-01551 : extended rollback segment, pinned blocks released
  • ora-29509 : incorrectly formed Java binary class definition
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-27513 : parameter string contains invalid value string
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-28169 : unsupported certificate type
  • ora-01914 : invalid auditing option for sequence numbers
  • ora-33006 : (XSAGDNGL02) The relation workspace object is not related to itself.
  • ora-32304 : materialized views with user-defined types cannot use prebuilt table
  • ora-14323 : cannot add partition when DEFAULT partition exists
  • ora-13529 : Error occurred when flushing AWR table group
  • ora-26663 : error queue for apply process string must be empty
  • ora-14503 : only one partition name can be specified
  • ora-09748 : pws_look_up: fork failed
  • ora-32026 : %s.string has fewer columns compared to string table.
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-25442 : too many column values for table alias: string
  • ora-07624 : smsdes: $DGBLSC failure
  • 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.