ORA-14196: Specified index cannot be used to enforce the constraint.

Cause : The indxe specifeid to enofrce thec onstraitn is unsiutable fro the puprose.

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

Specifya suitabel index ro allow noe to beb uilt auotmaticalyl.

update : 28-05-2017

ORA-14196 - Specified index cannot be used to enforce the constraint.
ORA-14196 - Specified index cannot be used to enforce the constraint.

  • ora-22813 : operand value exceeds system limits
  • ora-28279 : Error reading ldap_directory_access init parameter.
  • ora-28556 : authorization insufficient to access table
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-31096 : validation failed for schema
  • ora-39954 : DEFERRED is required for this system parameter
  • ora-37074 : (XSMCSESS02) Variable workspace object has no default aggmap.
  • ora-28055 : the password will expire within string days
  • ora-02754 : osnfsmmap: cannot change shared memory inheritence
  • ora-13855 : Tracing for service (module/action) string on instance string is already enabled
  • ora-22835 : Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
  • ora-26723 : user "string" requires the role "string"
  • ora-27412 : repeat interval or calendar contains invalid identifier: string
  • ora-06320 : IPA: Remote maximum number of connections exceeded
  • ora-19335 : Invalid format type object
  • ora-01693 : max # extents (string) reached in lob segment string.string
  • ora-30388 : name of the rewrite equivalence is not specified
  • ora-01683 : unable to extend index string.string partition string by string in tablespace string
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-25305 : enqueue failed, expiration must be zero for queue string.string
  • ora-09752 : pw_attachPorts: port_allocate failed.
  • ora-01092 : ORACLE instance terminated. Disconnection forced
  • ora-12832 : Could not allocate slaves on all specified instances
  • ora-16107 : all log data from primary has been processed
  • ora-32104 : cannot retrieve OCI error message
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-13278 : failure to convert SRID to native format
  • ora-13187 : subdivision failed
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-15062 : ASM disk is globally closed
  • 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.