ORA-14264: table is not partitioned by Composite Range method

Cause : The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method

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

Ensure that the table is partitioned by Composite method

update : 24-05-2017

ORA-14264 - table is not partitioned by Composite Range method
ORA-14264 - table is not partitioned by Composite Range method

  • ora-36722 : (XSALLOC02) In AGGMAP workspace object, you specified an NA or ZERO sourceval but supplied formula workspace object as your source for ALLOCATE.
  • ora-06515 : PL/SQL: unhandled exception string
  • ora-30654 : missing DEFAULT keyword
  • ora-39301 : schema "string" does not exist or is in use
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-16729 : validation of value for property string found string error
  • ora-13213 : failed to generate spatial index for window object
  • ora-13366 : invalid combination of interior exterior rings
  • ora-25001 : cannot create this trigger type on views
  • ora-01912 : ROW keyword expected
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-14276 : EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-22611 : TDS version is not recognized
  • ora-02217 : duplicate storage option specification
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-28028 : could not authenticate remote server
  • ora-12100 : materialized view log on "string"."string" already has sequence
  • ora-32640 : FOR LIKE loops are not allowed for multi-byte character types
  • ora-13140 : invalid target type
  • ora-03125 : client-server protocol violation
  • ora-16253 : Logical Standby cannot start due to incomplete terminal apply
  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-39176 : Encryption password is incorrect.
  • ora-01216 : thread string is expected to be disabled after CREATE CONTROLFILE
  • ora-13210 : error inserting data into the index table
  • ora-13447 : GeoRaster metadata BRS error
  • ora-35017 : (QFCHECK06) The Analytic Workspace and EIF file definitions of workspace object have different partitioning methods.
  • ora-36691 : (NTEXTCNV02) Invalid escape sequence in argument to UNISTR function: 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.