ORA-14012: resulting partition name conflicts with that of an existing partition

Cause : Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index

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

rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index

update : 29-04-2017

ORA-14012 - resulting partition name conflicts with that of an existing partition
ORA-14012 - resulting partition name conflicts with that of an existing partition

  • ora-00237 : snapshot operation disallowed: control file newly created
  • ora-16758 : the specified apply instance is not running
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-39727 : COMPATIBLE must be set to or higher
  • ora-30728 : maximum number of columns exceeded
  • ora-36162 : (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-37072 : (XSMCSESS00) Object workspace object has the wrong type.
  • ora-31654 : unable to convert file or volume size as specified to a number
  • ora-12921 : database is not in force logging mode
  • ora-29858 : error occurred in the execution of ODCIINDEXALTER routine
  • ora-29821 : specified primary operator does not exist
  • ora-14099 : all rows in table do not qualify for specified partition
  • ora-16502 : the Data Guard broker operation succeeded with warnings
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-08465 : input mask contains more than 32 characters
  • ora-06039 : NETDNT: connect failed
  • ora-14038 : GLOBAL partitioned index must be prefixed
  • ora-32155 : Anydata not specified
  • ora-29322 : SCN string size too long -- maximum size 58 bytes/characters
  • ora-29353 : The transportable list is too long.
  • ora-02217 : duplicate storage option specification
  • ora-25115 : duplicate BLOCK option specification
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-30574 : Cannot create rollback segment in tablespace with AUTO segment space management
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-29503 : SCHEMA keyword not valid with NAMED keyword
  • ora-14153 : only one of STORE IN or clause may be specified
  • ora-09885 : osnTXtt: cannot create TXIPC channel
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • 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.