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-05-2017
ORA-14626

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

  • ora-30569 : data type of given column is not supported in a log group
  • ora-24348 : Update or Delete without Where
  • ora-24198 : attempt to use an invalid operation ID
  • ora-25282 : message id. not provided for non-repudiation
  • ora-27250 : OS system call failure
  • ora-24804 : Lob read/write functions called while another OCI LOB read/write streaming is in progress
  • ora-03236 : max # extents (string) reached in index string.string subpartition string
  • ora-23424 : materialized view "string"."string" at string not registered
  • ora-10615 : Invalid tablespace type for temporary tablespace
  • ora-13364 : layer dimensionality does not match geometry dimensions
  • ora-23603 : STREAMS enqueue aborted due to low SGA
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-27059 : could not reduce file size
  • ora-30748 : column string already enabled to store objects of type string.string
  • ora-24012 : cannot drop QUEUE_TABLE, some queues in string have not been dropped
  • ora-30397 : multiple JOIN KEY clauses specified for the same child level
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-30341 : dropped level has references
  • ora-30453 : summary contains AVG without corresponding COUNT
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-37075 : (XSMCSESS03) You cannot rename a session-only dimension value.
  • ora-12350 : database link being dropped is still mounted
  • ora-28590 : agent control utility: illegal or badly formed command
  • ora-29295 : invalid mime header tag
  • ora-07201 : slhom: oracle_home variable not set in environment.
  • ora-22621 : error transfering an object from the agent
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • ora-01127 : database name 'string' exceeds size limit of string characters
  • 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.