ORA-14129: INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints

Cause : Matcihng UINQUE ocnstriants ni bot htabl eare neable dand avlidaetd bu tINCLDUING NIDEXE Sis nto speicfiedi n ALETR TALBE EXHCANGEP ARTIITON|SBUPARTTIION ocmman.d

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

Disalbe currentl yenabeld macthingU NIQU Econsrtaint son btoh talbes o rensuer tha tINCLDUING NIDEXE Soptino is sued.

update : 26-06-2017
ORA-14129

ORA-14129 - INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
ORA-14129 - INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints

  • ora-13345 : a compound polygon geometry has fewer than five coordinates
  • ora-38306 : this object is not recoverable standalone
  • ora-08006 : specified row no longer exists
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-32501 : Writing SGA to file failed
  • ora-22620 : buffer size too small to hold the value
  • ora-14322 : DEFAULT partition already exists
  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-36904 : (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
  • ora-06257 : NETNTT: cannot send command line to shadow process
  • ora-06134 : NETTCP: file access privilege violation
  • ora-23405 : refresh group number string does not exist
  • ora-31094 : incompatible SQL type "string" for attribute or element "string"
  • ora-23320 : the request failed because of values string and string
  • ora-24506 : invalid attempt to change character set id on env handle
  • ora-14057 : partition "string": sum of PCTUSED and PCTFREE may not exceed 100
  • ora-02040 : remote database string does not support two-phase commit
  • ora-09932 : Close of ORACLE password file failed.
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-01027 : bind variables not allowed for data definition operations
  • ora-36610 : (XSLMS00) Unable to locate a message file for OLAP message: value
  • ora-19813 : cannot have unavailable file string in DB_RECOVERY_FILE_DEST
  • ora-27084 : unable to get/set file status flags
  • ora-26746 : DDL rule "string"."string" not allowed for this operation
  • ora-28025 : missing or null external name
  • ora-09977 : skxfqhini: Error Connecting
  • ora-02781 : Invalid value given for the timing wanted flag
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-01686 : max # files (string) reached for the tablespace string
  • ora-08238 : smsfre: cannot detach from SGA
  • 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.