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 : 29-06-2017
ORA-14637

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

  • ora-02080 : database link is in use
  • ora-29534 : referenced object string.string could not be resolved
  • ora-00309 : log belongs to wrong database
  • ora-12983 : cannot drop all columns in a table
  • ora-23455 : flavor string contains object "string"
  • ora-21605 : property [string] is not a property of value instances
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-07706 : error in archive text: need disk file name
  • ora-13359 : extent does not have an area
  • ora-26670 : STREAMS option requires COMPATIBLE parameter to be string or higher
  • ora-39125 : Worker unexpected fatal error in string while calling string [string]
  • ora-02344 : cannot revoke execute on a type with table dependents
  • ora-22950 : cannot ORDER objects without MAP or ORDER method
  • ora-30690 : timeout occurred while registering a TCP/IP connection for data traffic detection
  • ora-14453 : attempt to use a LOB of a temporary table, whose data has alreadybeen purged
  • ora-04055 : Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-14048 : a partition maintenance operation may not be combined with other operations
  • ora-09809 : Unable to get user's group ID from connection
  • ora-24021 : queue table definition not imported for string.string
  • ora-13644 : The user "string" is invalid.
  • ora-24156 : duplicate table alias string
  • ora-07569 : slspool: $CLOSE failure
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-16003 : standby database is restricted to read-only access
  • ora-15106 : missing or invalid operating system disk locator string
  • ora-06771 : TLI Driver: error reading version
  • ora-01781 : UNRECOVERABLE cannot be specified without AS SELECT
  • ora-30966 : error detected in the XML Index layer
  • 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.