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-07-2017
ORA-14022

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

  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-28040 : No matching authentication protocol
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-29918 : cannot create domain indexes on temporary tables
  • ora-25214 : cannot specify delay or expiration for enqueue to exception queue
  • ora-37151 : MDX parser initialization error
  • ora-02236 : invalid file name
  • ora-29933 : object being disassociated has some user defined statistics stored
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-01080 : error in shutting down ORACLE
  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-16646 : Fast-Start Failover is disabled
  • ora-22065 : number to text translation for the given format causes overflow
  • ora-00286 : no members available, or no member contains valid data
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-39170 : Schema expression string does not correspond to any schemas.
  • ora-31065 : Cannot modify read-only property [string]
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • ora-16230 : committing transaction string string string
  • ora-01176 : data dictionary has more than the string files allowed by the controlfie
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-16177 : media recovery is not required
  • ora-25530 : FAST_START_MTTR_TARGET is not specified
  • ora-16704 : cannot modify a read-only property
  • ora-14026 : PARTITION and CLUSTER clauses are mutually exclusive
  • ora-12820 : invalid value for DEGREE
  • ora-36341 : (SNSYN130) The format of the PARTITIONCHECK function is: PARTITIONCHECK(aggmap, partition_template)
  • ora-31449 : invalid value for change_set_name
  • 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.