ORA-14188: sub-partitioning columns must form a subset of key columns of a UNIQUE index

Cause : User attempted to create a UNIQUE partitioned index whose sub-partitioning columns do not form a subset of its key columns which is illegal

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

If the user, indeed, desired to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index' subpartitioning columns form a subset of its key columns

update : 24-09-2017
ORA-14188

ORA-14188 - sub-partitioning columns must form a subset of key columns of a UNIQUE index
ORA-14188 - sub-partitioning columns must form a subset of key columns of a UNIQUE index

  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-08453 : more than one V symbol specified in picture mask
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-14309 : Total count of list values exceeds maximum allowed
  • ora-32135 : Cannot assign FILEs
  • ora-22063 : reading negative value [string] as unsigned
  • ora-01566 : file specified more than once in ALTER DATABASE
  • ora-22324 : altered type has compilation errors
  • ora-14323 : cannot add partition when DEFAULT partition exists
  • ora-28049 : the password has expired
  • ora-01875 : time zone minute must be between -59 and 59
  • ora-25533 : FAST_START_IO_TARGET or LOG_CHECKPOINT_INTERVAL is specified
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-36691 : (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: string.
  • ora-02067 : transaction or savepoint rollback required
  • ora-39067 : Unable to close the log file.
  • ora-19733 : COMPATIBLE parameter needs to be string or greater
  • ora-39771 : stream must be loaded before its handle is freed
  • ora-16221 : history table synchronization error
  • ora-12545 : Connect failed because target host or object does not exist
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-02376 : invalid or redundant resource
  • ora-01230 : cannot make read only - file string is offline
  • ora-32308 : object materialized views must use SELECT *
  • ora-02772 : Invalid maximum server idle time
  • ora-29539 : Java system classes already installed
  • ora-01675 : max_commit_propagation_delay inconsistent with other instances
  • ora-31601 : Function string cannot be called now that fetch has begun.
  • ora-09957 : Unable to send termination request to IMON
  • 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.