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 : 24-09-2017

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

  • ora-16147 : standby database referenced by multiple archive log destinations
  • ora-30657 : operation not supported on external organized table
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-15010 : name is already used by an existing ASM disk
  • ora-28530 : Heterogeneous Services initialization error in NLS language ID
  • ora-23620 : bind value size too large for PL/SQL CALL operation
  • ora-07513 : sscgctl: $deq unexpected return on cancel of term. lock
  • ora-16223 : DDL skipped, unsupported in current version
  • ora-01075 : you are currently logged on
  • ora-07432 : unable to perform nested sleep
  • ora-36405 : (XSSPROP05) Property ignored for object workspace object:
  • ora-07261 : spdde: kill error, unable to send signal to process.
  • ora-39065 : unexpected master process exception in string
  • ora-08234 : smsget: cannot get instance listener address
  • ora-01633 : Real Application Clusters Option needed for this operation
  • ora-23300 : %s
  • ora-10936 : trace name context forever
  • ora-00385 : cannot enable Very Large Memory with new buffer cache parameters
  • ora-16516 : the current state is invalid for the attempted operation
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-07275 : unable to send signal to process
  • ora-13860 : Invalid service name
  • ora-31637 : cannot create job string for user string
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-33005 : (XSAGDIMBREAK) Invalid breakout for dimension workspace object.
  • ora-30377 : table string.MV_CAPABILITIES_TABLE not found
  • ora-33267 : (DBERRRLS) Analytic workspace string cannot be accessed because it has fine-grained access control applied to it
  • ora-00073 : command string takes between string and string argument(s)
  • ora-31499 : null value specified for required parameter string
  • ora-01594 : attempt to wrap into rollback segment (string) extent (string) which is being freed
  • 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.