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 : 19-08-2017

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

  • ora-22863 : synonym for datatype string.string not allowed
  • ora-01977 : Missing thread number
  • ora-01334 : invalid or missing logminer dictionary processes context
  • ora-19280 : XQuery dynamic type mismatch: expected atomic value - got node
  • ora-13120 : invalid face_id [string]
  • ora-02338 : missing or invalid column constraint specification
  • ora-06533 : Subscript beyond count
  • ora-02083 : database name has illegal character 'string'
  • ora-24356 : internal error while converting from to COBOL display type.
  • ora-38775 : cannot disable flash recovery area - flashback database is enabled
  • ora-13417 : null or invalid layerNumber parameter
  • ora-24438 : Invalid Authentication Handle specified.
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-25444 : invalid ROWID: string for table alias: string
  • ora-39761 : stream reset required before loading this stream again
  • ora-01322 : No such table
  • ora-40286 : remote operations not permitted on mining models
  • ora-28003 : password verification for the specified password failed
  • ora-19603 : cannot backup or copy active file with KEEP .. UNRECOVERABLE option
  • ora-04029 : error ORA-string occurred when querying stringstringstring
  • ora-24084 : DBLINK name in address field of agent string is not unique within the first 24 bytes
  • ora-22894 : cannot add constraint on existing unscoped REF columns of non-empty tables
  • ora-14134 : indexes cannot use both DESC and REVERSE
  • ora-16532 : Data Guard broker configuration does not exist
  • ora-38503 : index already defined using the parameters
  • ora-01632 : max # extents (string) reached in index string.string
  • ora-01061 : cannot start up a V8 server using a V7 client application
  • ora-02734 : osnftt: cannot reset shared memory permission
  • ora-02485 : Invalid _trace_options parameter specification (string)
  • ora-02444 : Cannot resolve referenced object in referential constraints
  • 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.