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 : 21-08-2017

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

  • ora-12500 : TNS:listener failed to start a dedicated server process
  • ora-07757 : slemcc: invalid handle
  • ora-10571 : Test recovery canceled
  • ora-04017 : invalid value string (length = string) for parameter max_dump_file_size
  • ora-00337 : log file 'string' does not exist and no size specified
  • ora-07740 : slemop: incorrect handle size (programming error)
  • ora-38793 : cannot FLASHBACK the database to a future SCN/time
  • ora-10570 : Test recovery complete
  • ora-06312 : IPA: Incorrect outgoing service name supplied
  • ora-01883 : overlap was disabled during a region transition
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-31648 : Timeout before master process string finished initialization.
  • ora-30964 : The XML Index was not usable.
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-31088 : object "string"."string" depends on the schema
  • ora-00394 : online log reused while attempting to archive it
  • ora-24434 : OCIStmtRelease called before OCIStmtPrepare2.
  • ora-03200 : the segment type specification is invalid
  • ora-31668 : Timeout before worker process string finished initialization.
  • ora-06913 : CMX: error during redirection of connection
  • ora-14151 : invalid table partitioning method
  • ora-27199 : skgfpst: sbtpcstatus returned error
  • ora-01575 : timeout waiting for space management resource
  • ora-30938 : No prefix defined for namespace 'string' (particle string)
  • ora-19810 : Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
  • ora-15178 : directory 'string' is not empty; cannot drop this directory
  • ora-16132 : An error occurred during activation of the standby.
  • ora-13356 : adjacent points in a geometry are redundant
  • ora-02461 : Inappropriate use of the INDEX option
  • ora-00480 : LCK* process terminated with error
  • 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.