ORA-25199: partitioning key of a index-organized table must be a subset of the primary key

Cause : An attempt to specify a partitioning key which is not a prefix of the primary key of the index-organized table

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

Select a different partitioning key

update : 17-08-2017

ORA-25199 - partitioning key of a index-organized table must be a subset of the primary key
ORA-25199 - partitioning key of a index-organized table must be a subset of the primary key

  • ora-39003 : unable to get count of total workers alive
  • ora-21779 : duration not active
  • ora-10900 : extent manager fault insertion event #string
  • ora-04031 : unable to allocate string bytes of shared memory ("string","string","string","string")
  • ora-29523 : authorization error for unknown referenced name
  • ora-13011 : value is out of range
  • ora-00820 : Specified value of sga_max_size is too small, needs to be at least stringM
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-36638 : (XSDUNION17) Concat dimension workspace object cannot be changed to UNIQUE because it has a non-unique concat base dimension workspace object.
  • ora-24365 : error in character conversion
  • ora-02077 : selects of long columns must be from co-located tables
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-02007 : can't use ALLOCATE or DEALLOCATE options with REBUILD
  • ora-40102 : invalid input string for data mining operation string
  • ora-12073 : request cannot be processed
  • ora-37151 : MDX parser initialization error
  • ora-29277 : invalid SMTP operation
  • ora-12597 : TNS:connect descriptor already in use
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-12729 : invalid character class in regular expression
  • ora-27076 : unable to set limit for open files
  • ora-24368 : OCI mutex counter non-zero when freeing a handle
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-24354 : number fetched too large to fit in COBOL display type buffer.
  • ora-07707 : error in archive text: need tape label name
  • ora-19613 : datafile string not found in backup set
  • ora-01524 : cannot create data file as 'string' - file already part of database
  • ora-27548 : Unable to unprepare IPC buffer
  • ora-16530 : invalid buffer or length
  • ora-29845 : indextype does not support local domain index on string partitioned table
  • 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.