ORA-14627: Invalid operation was specified on a GLOBAL partitioned index

Cause : An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index

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

Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned

update : 29-04-2017
ORA-14627

ORA-14627 - Invalid operation was specified on a GLOBAL partitioned index
ORA-14627 - Invalid operation was specified on a GLOBAL partitioned index

  • ora-10634 : Segment is already being shrunk
  • ora-01636 : rollback segment 'string' is already online
  • ora-25183 : index-organized table top index segment is in a different tablespace
  • ora-06607 : LU6.2 Driver: Reset occurred in send state
  • ora-28268 : Exceeded the maximum allowed size for Context information in a session
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-22929 : invalid or missing directory name
  • ora-24758 : not attached to the requested transaction
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-01262 : Stat failed on a file destination directory
  • ora-01639 : instance string has no thread assigned to it
  • ora-12704 : character set mismatch
  • ora-29862 : cannot specify FORCE option for dropping non-domain index
  • ora-30100 : internal error [number]
  • ora-34286 : (MXDCL53) workspace object cannot be used in this context because it is a string.
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-01466 : unable to read data - table definition has changed
  • ora-13016 : specified topology [string] is invalid
  • ora-02347 : cannot grant privileges on columns of an object table
  • ora-01519 : error while processing file 'string' near line string
  • ora-02716 : osnpgetdatmsg: message from host had incorrect message type
  • ora-24157 : duplicate variable name string
  • ora-31480 : staging database and source database cannot be the same
  • ora-24235 : bad value for object type: string
  • ora-02332 : cannot create index on attributes of this column
  • ora-14006 : invalid partition name
  • ora-13181 : unable to determine length of column string_SDOINDEX.SDO_CODE
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • 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.