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-04-2017

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-12708 : error while loading create database NLS parameter string
  • ora-19501 : read error on file "string", blockno string (blocksize=string)
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-25466 : data not specified for variable name: string
  • ora-16138 : end of log stream not received from primary
  • ora-02820 : Unable to write the requested number of blocks
  • ora-01422 : exact fetch returns more than requested number of rows
  • ora-38954 : Cross platform transport is not supported between source platform identifier string and target platform identifier string
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-02048 : attempt to begin distributed transaction without logging on
  • ora-25285 : Invalid value string for array_mode
  • ora-16121 : applying transaction with commit SCN string
  • ora-12086 : table "string"."string" is not an object table
  • ora-32055 : invalid file type
  • ora-22903 : MULTISET expression not allowed
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-19568 : a device is already allocated to this session
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-39780 : Direct path context operations are not allowed after the context is aborted or finished
  • ora-16516 : the current state is invalid for the attempted operation
  • ora-32003 : error occured processing parameter 'string'
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-14024 : number of partitions of LOCAL index must equal that of the underlying table
  • ora-10565 : Another test recovery session is active
  • ora-15192 : invalid ASM disk header [string] [string] [string] [string] [string]
  • ora-39088 : file name cannot contain a path specification
  • ora-39030 : invalid file type string
  • ora-23417 : unknown materialized view type: string
  • ora-23470 : invalid status
  • ora-40213 : contradictory values for settings: string, string
  • 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.