ORA-14022: creation of LOCAL partitioned cluster indices is not supported

Cause : An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal

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

Remove LOCAL along with s, if any, from the CREATE INDEX statement.

update : 26-04-2017

ORA-14022 - creation of LOCAL partitioned cluster indices is not supported
ORA-14022 - creation of LOCAL partitioned cluster indices is not supported

  • ora-01665 : control file is not a standby control file
  • ora-21706 : duration does not exist or is invalid
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-00480 : LCK* process terminated with error
  • ora-08000 : maximum number of session sequence lists exceeded
  • ora-27433 : cannot alter state of step string for job string.string to string
  • ora-09925 : Unable to create audit trail file
  • ora-00376 : file string cannot be read at this time
  • ora-36270 : (XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values.
  • ora-26536 : refresh was aborted because of conflicts caused by deferred transactions
  • ora-00055 : maximum number of DML locks exceeded
  • ora-12471 : Specified compartment or group is not authorized for user
  • ora-16600 : failover operation can only be submitted at target database
  • ora-13625 : %s is an invalid advisor object type.
  • ora-31409 : one or more values for input parameters are incorrect
  • ora-12487 : clearance labels not between DBHIGH and DBLOW
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-36402 : (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
  • ora-24199 : message store is overflow
  • ora-13422 : invalid model coordinate parameter
  • ora-16157 : media recovery not allowed following successful FINISH recovery
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-01559 : MAXEXTENTS for rollback segment must be greater than 1
  • ora-31508 : invalid parameter value for synchronous change set
  • ora-29320 : datafile header error
  • ora-01987 : client os username is too long
  • ora-01171 : datafile string going offline due to error advancing checkpoint
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-24402 : error occured while creating connections in the pool
  • 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.