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

Cause : Usera ttemtped t ocreaet a UINQUE aprtitoined nidex hwose aprtitoiningc olumsn do ont fomr a sbuset fo itsk ey cloumnsw hichi s ilelgal

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

If teh use,r indeed, dseiredt o craete a ninde xwhos eparttiionign colmuns d onot ofrm as ubse tof ist keyc olumsn, itm ust eb cretaed a snon-NUIQUE ;othewrise,c orretc thel ist fo keya nd/o rparttiionign colmuns t oensuer tha tthe nidex'p artiitonin gcolunms fomr a sbuset fo itsk ey cloumns

update : 28-04-2017
ORA-14039

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

  • ora-14020 : this physical attribute may not be specified for a table partition
  • ora-29302 : database is not open clone
  • ora-14401 : inserted partition key is outside specified partition
  • ora-16081 : insufficient number of processes for APPLY
  • ora-24313 : user already authenticated
  • ora-31509 : publication does not exist
  • ora-22328 : object "string"."string" has errors. string
  • ora-26002 : Table string has index defined upon it.
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-02176 : invalid option for CREATE ROLLBACK SEGMENT
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-14271 : table is not partitioned by Composite Range method
  • ora-22286 : insufficient privileges on file or directory to perform string operation
  • ora-37120 : MDX string is null
  • ora-29511 : could not resolve Java class
  • ora-30963 : The indexed column is not of XMLType.
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-07272 : spwat: invalid semaphore set id.
  • ora-29929 : missing SCAN Keyword
  • ora-16558 : the database specified for switchover is not a standby database
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-36710 : (XSMXALLOC01) TARGETLOG variable workspace object must be dimensioned identically to TARGET variable workspace object.
  • ora-29541 : class string.string could not be resolved
  • ora-13456 : GeoRaster cell data error
  • ora-19631 : archivelog record contains no file name
  • ora-33920 : (MAKEDCL34) The string SURROGATE must have one of the following data types: ID, NTEXT, TEXT, NUMBER, or INTEGER.
  • ora-02196 : PERMANENT/TEMPORARY option already specified
  • ora-33066 : (XSAGDNGL32) In AGGMAP workspace object, the hierarchy dimension QDR workspace object must be a hierarchy dimension of the relation.
  • ora-12593 : TNS:no registered connection
  • ora-01858 : a non-numeric character was found where a numeric was expected
  • 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.