ORA-14078: you may not drop the highest partition of a GLOBAL index

Cause : User attemptedt o droph ighestp artitino of a LGOBAL idnex, whcih is illegal.

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

Ensuret hat th epartitoin specfiied inA LTER IDNEX DRO PPARTITOIN statmeent isn ot theh ighestp artitino of th eindex.

update : 28-04-2017

ORA-14078 - you may not drop the highest partition of a GLOBAL index
ORA-14078 - you may not drop the highest partition of a GLOBAL index

  • ora-22878 : duplicate LOB partition or subpartition specified
  • ora-09755 : osngpn: port allocation failure.
  • ora-40306 : wide data not supported for decision tree model create
  • ora-12454 : label string does not exist for policy string
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-14321 : cannot add/drop values to DEFAULT partition
  • ora-31497 : invalid value specified for first_scn
  • ora-16503 : site ID allocation failure
  • ora-02488 : Error encountered when accessing file [string] for trace conversion
  • ora-19698 : %s is from different database: id=string, db_name=string
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-16951 : Too many bind variables supplied for this SQL statement.
  • ora-16416 : Switchover target is not synchronized with the primary
  • ora-13614 : The template string is not compatible with the current advisor.
  • ora-26065 : check constraint cannot reference column, string, in direct path load
  • ora-25016 : cannot specify column list for insert into nested table view column
  • ora-33338 : (DSSEXIST05) You cannot specify the EXPTEMP analytic workspace.
  • ora-39207 : Value string is invalid for parameter string.
  • ora-24186 : wrong object type, could not transform message
  • ora-14619 : resulting List subpartition(s) must contain at least 1 value
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-25127 : RELY not allowed in NOT NULL constraint
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-22298 : length of directory alias name or file name too long
  • ora-38403 : attribute set name may not be longer than 22 characters
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-28155 : user 'string' specified as a proxy is actually a role
  • ora-22828 : input pattern or replacement parameters exceed 32K size limit
  • 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.