ORA-14274: partitions being merged are not adjacent

Cause : User attempt to merge two partitions that are not adjacent to each other which is illegal

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

Specify two partitions that are adjacent

update : 30-04-2017
ORA-14274

ORA-14274 - partitions being merged are not adjacent
ORA-14274 - partitions being merged are not adjacent

  • ora-15020 : discovered duplicate ASM disk "string"
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-10943 : trace name context forever
  • ora-22850 : duplicate LOB storage option specificed
  • ora-03217 : invalid option for alter of TEMPORARY TABLESPACE
  • ora-38762 : thread string redo log with scn string could not be found
  • ora-07406 : slbtpd: invalid number.
  • ora-19801 : initialization parameter DB_RECOVERY_FILE_DEST is not set
  • ora-12590 : TNS:no I/O buffer
  • ora-38738 : Flashback log file is not current copy.
  • ora-26078 : file "string" is not part of database being loaded
  • ora-14157 : invalid subpartition name
  • ora-01203 : wrong incarnation of this file - wrong creation SCN
  • ora-01604 : illegal number range in clause "string" of string
  • ora-16602 : object must be disabled to perform this operation
  • ora-06436 : ssaio: asynchronous I/O failed due to incorrect parameters.
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-25108 : standby lock name space exceeds size limit of string characters
  • ora-23490 : extension request "string" with status "string" not allowed in this operation
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-35095 : (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated.
  • ora-14318 : DEFAULT partition must be last partition specified
  • ora-06033 : NETDNT: connect failed, partner rejected connection
  • ora-19957 : database should have no datafiles in unknown state
  • ora-02097 : parameter cannot be modified because specified value is invalid
  • ora-38419 : invalid identifier in attribute : string
  • ora-30374 : materialized view is already fresh
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-12502 : TNS:listener received no CONNECT_DATA from client
  • ora-06951 : Operating system call error
  • 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.