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 : 23-08-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-07285 : sksaprd: volume size should not be specified for a disk file.
  • ora-01573 : shutting down instance, no further change allowed
  • ora-30071 : conversion between datetime/interval and string fail
  • ora-07629 : smpall: $EXPREG failure
  • ora-19598 : can not backup SPFILE because the instance was not started with SPFILE
  • ora-15070 : maximum number of files string exceeded in diskgroup "string"
  • ora-29880 : such column list already indexed using another domain index and indextype
  • ora-06128 : NETTCP: unable to create mailbox
  • ora-32118 : Cannot perform operation on a null FILE
  • ora-40204 : model string already exists
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-00030 : User session ID does not exist.
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-00444 : background process "string" failed while starting
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-02327 : cannot create index on expression with datatype string
  • ora-06808 : TLI Driver: could not link IPX and ethernet streams
  • ora-23621 : Operation corresponding to script string is in progress.
  • ora-31634 : job already exists
  • ora-22854 : invalid option for LOB storage index
  • ora-06924 : CMX: wrong break message length
  • ora-32127 : REFs do not belong to any connection
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-12987 : cannot combine drop column with other operations
  • ora-24753 : local transactions cannot be detached
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-07707 : error in archive text: need tape label name
  • ora-28048 : database is a member of multiple enterprise domains in OID
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-30181 : integer in argument index is not immediately followed by )
  • 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.