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 : 25-06-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-19102 : XQuery string literal expected
  • ora-31187 : Cannot Add Node 'string' (type='string') to Simple Type Node 'string'
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-16257 : Switchover initiated stop apply successfully completed
  • ora-13143 : invalid POLYGON window definition
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-38475 : The attribute set and the associated ADT are out of sync.
  • ora-13779 : invalid load option
  • ora-40302 : invalid classname string in cost matrix specification
  • ora-13709 : Required parameter "string" must be set before execution.
  • ora-37103 : (XSVPART03) The dimensionality or datatype of workspace object does not match the dimensionality or datatype of the partition.
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-14257 : cannot move partition other than a Range or Hash partition
  • ora-13040 : failed to subdivide tile
  • ora-21526 : initialization failed
  • ora-30656 : column type not supported on external organized table
  • ora-26519 : no memory available to allocate
  • ora-16550 : truncated result
  • ora-22626 : Type Mismatch while constructing or accessing OCIAnyData
  • ora-04067 : not executed, string does not exist
  • ora-31691 : The worker received message number string from the MCP, which is invalid.
  • ora-06749 : TLI Driver: option not allowed across network
  • ora-19229 : XP0009 - schema import not supported
  • ora-19100 : PASSING or RETURNING keyword expected
  • ora-25143 : default storage clause is not compatible with allocation policy
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-02842 : Client unable to fork a server
  • ora-24280 : invalid input value for parameter string
  • ora-06802 : TLI Driver: could not open the /etc/netware/yellowpages file
  • ora-30556 : functional index is defined on the column to be modified
  • 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.