ORA-14635: only one resulting subpartition can be specified for MERGE SUBPARTITIONS

Cause : ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE

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

Ensure that the statement describes exactly one subpartition as the target that need to be MERGEd

update : 23-05-2017
ORA-14635

ORA-14635 - only one resulting subpartition can be specified for MERGE SUBPARTITIONS
ORA-14635 - only one resulting subpartition can be specified for MERGE SUBPARTITIONS

  • ora-12665 : NLS string open failed
  • ora-23379 : connection qualifier "string" is too long
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-31112 : fail to string for string port using xdb configuration
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-00300 : illegal redo log block size string specified - exceeds limit of string
  • ora-00268 : specified log file does not exist 'string'
  • ora-16125 : large transaction string string string is waiting for more data
  • ora-04093 : references to columns of type LONG are not allowed in triggers
  • ora-19924 : there are no row with id string
  • ora-32742 : Hang analysis initialize failed
  • ora-30347 : a table name is required to qualify the column specification
  • ora-08197 : Flashback Table operation is not supported on clustered tables
  • ora-32630 : multiple assignment in automatic order MODEL
  • ora-39084 : cannot detach job string for user string
  • ora-01980 : error during OS ROLE initialization
  • ora-38464 : expression set is not empty.
  • ora-35016 : (QFCHECK00) The analytic workspace and EIF file definitions of workspace object have a mismatched type.
  • ora-02062 : distributed recovery received DBID string, expected string
  • ora-07256 : sptrap: cannot set up signal handler to catch exceptions.
  • ora-12159 : TNS:trace file not writeable
  • ora-23468 : missing string string
  • ora-27121 : unable to determine size of shared memory segment
  • ora-14322 : DEFAULT partition already exists
  • ora-32627 : illegal pattern in MODEL FOR LIKE loop
  • ora-00384 : Insufficient memory to grow cache
  • ora-39205 : Transforms are not supported in transportable jobs.
  • ora-07503 : scgcmn: $setimr unexpected return
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-38704 : Checksum error in flashback database log file header.
  • 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.