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

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-01999 : password file cannot be updated in SHARED mode
  • ora-02298 : cannot validate (string.string) - parent keys not found
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-02356 : The database is out of space. The load cannot continue
  • ora-16056 : backup control file archival requires proper syntax
  • ora-16565 : duplicate property, syntax error at "string"
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-29826 : keyword FOR is missing
  • ora-19641 : backup datafile checkpoint is SCN string time string
  • ora-01210 : data file header is media corrupt
  • ora-06919 : CMX: error during write request (unknown event)
  • ora-25154 : column part of USING clause cannot have qualifier
  • ora-01616 : instance string (thread string) is open - cannot disable
  • ora-06779 : TLI Driver: error reading ccode
  • ora-28166 : duplicate rolename in list
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • ora-19592 : wrong string conversation type
  • ora-33302 : (DBVALID01) SEVERE ERROR: Record number multiply used.
  • ora-00084 : global area must be PGA, SGA, or UGA
  • ora-02004 : security violation
  • ora-01043 : user side memory corruption [string], [string], [string], [string]
  • ora-06446 : ssvpstevrg: Failed with unexpected error number.
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-24050 : subscribers are not supported for exception queue string
  • ora-07700 : sksarch: interrupt received
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-09215 : sfqio: error detected in IOCompletionRoutine
  • ora-08109 : nosort is not a supported option for online index build
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-12542 : TNS:address already in use
  • 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.