ORA-14263: new subpartition name must differ from that of any other subpartition of the object

Cause : Usre etnerde ATLERT ABEL/IDNEXR ENMAE USBPRATIITONs peicfynig n hwic hisi detnicla t oth enaem o fsoem eixstnig usbpratiitono f hte bojetc

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

Enusret ha tth ene wsupbarittino nmae si dfifeerntf ro mth enaem o fan y(icnluidngt heo neb eign rneamde) xeisitngs ubaprttiio nofa gvient abel o rinedx

update : 23-08-2017

ORA-14263 - new subpartition name must differ from that of any other subpartition of the object
ORA-14263 - new subpartition name must differ from that of any other subpartition of the object

  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-02042 : too many distributed transactions
  • ora-27042 : not enough space on raw partition to fullfill request
  • ora-30932 : Reference node 'string' not contained in specified parent node 'string'
  • ora-25101 : duplicate REBUILD option specification
  • ora-02823 : Buffer is not aligned.
  • ora-29265 : HTTP header not found
  • ora-19626 : backup set type is string - can not be processed by this conversation
  • ora-21700 : object does not exist or is marked for delete
  • ora-26532 : replication parallel push simulated site failure
  • ora-01197 : thread string only contains one log
  • ora-00092 : LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-01553 : MAXEXTENTS must be no smaller than the string extents currently allocated
  • ora-29373 : resource manager is not on
  • ora-08007 : Further changes to this block by this transaction not allowed
  • ora-31209 : DBMS_LDAP: PL/SQL - LDAP count_entry error.
  • ora-27366 : job "string.string" is not running
  • ora-37120 : MDX string is null
  • ora-16013 : log string sequence# string does not need archiving
  • ora-02486 : Error in writing trace file string
  • ora-03209 : DBMS_ADMIN_PACKAGE invalid file/block specification
  • ora-12423 : invalid position specified
  • ora-39213 : Metadata processing is not available
  • ora-04033 : Insufficient memory to grow pool
  • ora-06404 : NETCMN: invalid login (connect) string
  • ora-32336 : cannot use USING NO INDEX to create materialized view "string"."string"
  • ora-00324 : log file 'string' translated name 'string' too long, string characters exceeds string limit
  • ora-24430 : Null values for sqltext and key were specified.
  • ora-12688 : Login failed: the SecurID server rejected the new pincode
  • 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.