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 : 19-08-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-12820 : invalid value for DEGREE
  • ora-13288 : point coordinate transformation error
  • ora-23366 : integer value string is less than 1
  • ora-01511 : error in renaming log/data files
  • ora-19730 : can not convert offline plugged-in datafile string
  • ora-31679 : Table data object string has long columns, and longs can not be loaded/unloaded using a network link
  • ora-13904 : The file has been dropped and recreated during the procedure call.
  • ora-39050 : parameter string is incompatible with parameter string
  • ora-02405 : invalid sql plan object provided
  • ora-12683 : encryption/crypto-checksumming: no Diffie-Hellman seed
  • ora-13231 : failed to create index table [string] during R-tree creation
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • ora-22850 : duplicate LOB storage option specificed
  • ora-22617 : error while accessing the image handle collection
  • ora-16509 : the request timed out
  • ora-01985 : cannot create user as LICENSE_MAX_USERS parameter exceeded
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-13601 : The specified Advisor string does not exist.
  • ora-06604 : LU6.2 Driver: Unable to allocate session with remote LU
  • ora-00107 : failed to connect to ORACLE listener process
  • ora-13783 : invalid tuning scope
  • ora-06115 : NETTCP: unable to create ORACLE logicals
  • ora-28349 : cannot encrypt the specified column recorded in the materialized view log
  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-01523 : cannot rename data file to 'string' - file already part of database
  • ora-01672 : control file may be missing files or have extra ones
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-24852 : protocol error during statement execution
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-09967 : unable to create or open lock 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.