ORA-14640: add/coalesce index partition operation is valid only for hash partitioned global indexes

Cause : User tatemptde to add or caolescea n indxe parttiion o fa gloabl indxe not aprtitinoed byh ash mtehod.

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

Issuet he sttaemento n a golbal idnex patritionde by hsah metohd. ori f thei ndex si parttiionedb y raneg methdo consdier usnig splti/dropi nstea dof ad/dcoalecse.

update : 21-08-2017

ORA-14640 - add/coalesce index partition operation is valid only for hash partitioned global indexes
ORA-14640 - add/coalesce index partition operation is valid only for hash partitioned global indexes

  • ora-00034 : cannot string in current PL/SQL session
  • ora-25105 : RECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-30501 : instance shutdown triggers cannot have AFTER type
  • ora-08004 : sequence string.NEXTVAL string stringVALUE and cannot be instantiated
  • ora-31215 : DBMS_LDAP: PL/SQL - Invalid LDAP mod value.
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-12646 : Invalid value specified for boolean parameter
  • ora-30042 : Cannot offline the undo tablespace
  • ora-29376 : number of consumer groups string in top-plan string exceeds string
  • ora-00266 : name of archived log file needed
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-06915 : CMX: unknown t_event in datarq
  • ora-27029 : skgfrtrv: sbtrestore returned error
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-03250 : Cannot mark this segment corrupt
  • ora-09820 : Conversion of class string to numeric representation failed.
  • ora-04053 : error occurred when validating remote object stringstringstringstringstring
  • ora-12924 : tablespace string is already in force logging mode
  • ora-09983 : skxfidsht: Error shutting down SDI channel
  • ora-01576 : The instance string is not enabled
  • ora-12031 : cannot use primary key columns from materialized view log on "string"."string"
  • ora-01353 : existing Logminer session
  • ora-27509 : IPC error receiving a message
  • ora-12212 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-01112 : media recovery not started
  • ora-15057 : specified size of string MB is larger than actual size of string MB
  • ora-02399 : exceeded maximum connect time, you are being logged off
  • ora-01877 : string is too long for internal buffer
  • ora-30193 : reserved for future use
  • ora-02764 : Invalid package mode
  • 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.