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 : 26-06-2017

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-01285 : error reading file string
  • ora-23301 : mixed use of deferred rpc destination modes
  • ora-24273 : translation text is required if translation type is T or S
  • ora-27208 : syntax error in device PARMS - environment variable value missing
  • ora-02796 : Done request is not in correct state
  • ora-30556 : functional index is defined on the column to be modified
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • ora-27212 : some entrypoints in Media Management Library are missing
  • ora-01593 : rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)
  • ora-01624 : log string needed for crash recovery of instance string (thread string)
  • ora-01114 : IO error writing block to file string (block # string)
  • ora-38485 : invalid object type for the user-defined function
  • ora-28168 : attempted to grant password-protected role
  • ora-16056 : backup control file archival requires proper syntax
  • ora-02283 : cannot alter starting sequence number
  • ora-19666 : cannot do incremental restore of the control file
  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-19716 : error processing format string to generate name for backup
  • ora-31462 : internal error while accessing metadata
  • ora-07578 : szprv: $FIND_HELD failure
  • ora-00056 : DDL lock on object 'string.string' is already held in an incompatible mode
  • ora-13192 : failed to read number of element rows
  • ora-00397 : instance recovery process terminated with error
  • ora-10577 : Can not invoke test recovery for managed standby database recovery
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-23493 : "string" is not a new site for extension request "string"
  • ora-10262 : Don't check for memory leaks
  • ora-14138 : An unexpected error encountered during drop table operation
  • ora-13905 : Critical or warning threshold have incorrect values
  • ora-31620 : file or device "string" cannot be specified for string operation
  • 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.