ORA-14626: values being added already exist in DEFAULT subpartition

Cause : An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition

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

Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added

update : 28-07-2017
ORA-14626

ORA-14626 - values being added already exist in DEFAULT subpartition
ORA-14626 - values being added already exist in DEFAULT subpartition

  • ora-12073 : request cannot be processed
  • ora-09870 : spini: failure initializing maximum number of open files.
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-09832 : infoCallback: bad message format.
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-28100 : policy function schema string is invalid
  • ora-06002 : NETASY: port read failure
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-19010 : Cannot insert XML fragments
  • ora-13221 : unknown geometry type in the geometry object
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-02093 : TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)
  • ora-00991 : only MAC privileges may be granted to procedures
  • ora-03128 : connection is in blocking mode
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-29859 : error occurred in the execution of ODCIINDEXTRUNCATE routine
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-24372 : invalid object for describe
  • ora-19731 : cannot apply change to unverified plugged-in datafile string
  • ora-32021 : parameter value longer than string characters
  • ora-24068 : cannot start queue string, queue table string is being migrated
  • ora-16194 : Modifying DB_UNIQUE_NAME requires SID='*' qualifier
  • ora-14645 : STORE IN clause cannot be specified for Range List objects
  • ora-02183 : valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-32059 : deadlock detected on mapping structures
  • ora-06711 : TLI Driver: error on bind
  • ora-25157 : Specified block size string is not valid
  • ora-23396 : database link "string" does not exist or has not been scheduled
  • ora-27069 : attempt to do I/O beyond the range of the file
  • 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.