ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive

Cause : defniitino ofa talbe cnotaiend btoh PRATITOIN adn CLSUTERc lauess wihch si ilelgal

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

Remvoe oen oft he ocnflcitin gclasues

update : 26-06-2017
ORA-14026

ORA-14026 - PARTITION and CLUSTER clauses are mutually exclusive
ORA-14026 - PARTITION and CLUSTER clauses are mutually exclusive

  • ora-22917 : use VARRAY to define the storage clause for this column or attribute
  • ora-14174 : only a may follow COALESCE PARTITION|SUBPARTITION
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-07759 : slemtr: invalid destination
  • ora-09821 : Numeric label is not valid
  • ora-02451 : duplicate HASHKEYS specification
  • ora-38430 : Operation "string" not supported in the current release.
  • ora-01519 : error while processing file 'string' near line string
  • ora-38781 : cannot disable media recovery - have guaranteed restore points
  • ora-00380 : cannot specify db_stringk_cache_size since stringK is the standard block size
  • ora-27034 : maximum length of ORACLE_SID exceeded
  • ora-29270 : too many open HTTP requests
  • ora-32302 : object materialized views must be object ID based
  • ora-15181 : Symbol [string] not found in library string, error [string]
  • ora-14513 : partitioning column may not be of object datatype
  • ora-30336 : no child for specified JOIN KEY
  • ora-30505 : system triggers should not reference a column in a WHEN clause
  • ora-30362 : dimension column cannot be a sequence
  • ora-12468 : max write level does not equal max read level
  • ora-36671 : (XSDPART09) Leaves of workspace object have different datatypes. A partition dimension cannot have more than one datatype when RANGE partitioning is used.
  • ora-19698 : %s is from different database: id=string, db_name=string
  • ora-31089 : schema "string" does not target namespace "string"
  • ora-25310 : Subscriber is Notification only; dequeue not supported
  • ora-39043 : Object type string is not supported for string.
  • ora-36884 : (XSSRF03) The value of the first parameter of the AW single row function is incorrect.
  • ora-30370 : set operators are not supported in this context
  • ora-31402 : unrecognized parameter string
  • ora-13333 : invalid LRS measure
  • ora-10945 : trace name context forever
  • ora-03250 : Cannot mark this segment corrupt
  • 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.