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 : 27-04-2017
ORA-14196

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

  • ora-24810 : attempting to write more data than indicated
  • ora-06518 : PL/SQL: Probe version string incompatible with version string
  • ora-29847 : cannot create a local domain index on a partitioned index-organized table
  • ora-31167 : XML nodes over 64K in size cannot be inserted
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • ora-01923 : CASCADE aborted, objects locked by another user
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • ora-38959 : Failed to update block 0 to new version 10 format
  • ora-13830 : SQL profile with category string already exists for this SQL statement
  • ora-01693 : max # extents (string) reached in lob segment string.string
  • ora-31099 : XDB Security Internal Error
  • ora-22902 : CURSOR expression not allowed
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-32032 : free temporary object number not available
  • ora-02732 : osnrnf: cannot find a matching database alias
  • ora-31419 : source table string does not exist
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-19109 : RETURNING keyword expected
  • ora-31100 : XDB Locking Internal Error
  • ora-38764 : flashback not started; datafile string enabled threads are different
  • ora-00301 : error in adding log file 'string' - file cannot be created
  • ora-19101 : CONTENT keyword expected
  • ora-16411 : ONDEMAND archival requires active managed recovery operation
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-14049 : invalid ALTER TABLE MODIFY PARTITION option
  • ora-15103 : conflicting or duplicate REPAIR options
  • ora-13498 : %s
  • ora-28100 : policy function schema string is invalid
  • 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.