ORA-14637: cannot merge a subpartition with itself

Cause : The same subpartition name was specified twice for the merge operation

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

Re-submit operation with 2 distinct subpartition names within the same composite partition

update : 17-08-2017

ORA-14637 - cannot merge a subpartition with itself
ORA-14637 - cannot merge a subpartition with itself

  • ora-22953 : Cardinality of the input to powermultiset exceeds maximum allowed
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-30683 : failure establishing connection to debugger
  • ora-01603 : illegal grouping size in clause "string" of string
  • ora-09811 : Unable to initialize package.
  • ora-01411 : cannot store the length of column in the indicator
  • ora-29534 : referenced object string.string could not be resolved
  • ora-01685 : max # extents (string) reached in index string.string partition string
  • ora-29544 : invalid type
  • ora-24771 : cannot detach, prepare or forget a local transaction
  • ora-12157 : TNS:internal network communication error
  • ora-39078 : unable to dequeue message for agent string from queue "string"
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-01051 : deferred rpc buffer format invalid
  • ora-15205 : requested mirror side unavailable
  • ora-22060 : argument [string] is an invalid or uninitialized number
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-16230 : committing transaction string string string
  • ora-29825 : invalid name for indextype
  • ora-02266 : unique/primary keys in table referenced by enabled foreign keys
  • ora-38908 : internal error occurred during DML Error Logging
  • ora-22887 : type of REF column is not the same as that of its scoped table
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-10382 : parallel query server interrupt (reset)
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-00383 : DEFAULT cache for blocksize string cannot be reduced to zero
  • ora-01151 : use media recovery to recover block, restore backup if needed
  • ora-01128 : cannot start online backup - file string is offline
  • ora-06700 : TLI Driver: incorrect message type from host
  • 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.