ORA-14081: new partition name must differ from the old partition name

Cause : User entered ALTER TABLE/INDEX RENAME PARTITION specifying which is identical to the name of the partition being renamed

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

Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index

update : 20-08-2017
ORA-14081

ORA-14081 - new partition name must differ from the old partition name
ORA-14081 - new partition name must differ from the old partition name

  • ora-00125 : connection refused; invalid presentation
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-39956 : duplicate setting for PL/SQL compiler parameter string
  • ora-28142 : error in accessing audit index file
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-28362 : master key not found
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-14605 : Name missing for subpartition / lob segment in template
  • ora-00606 : Internal error code
  • ora-19923 : the session for row with id string is not active
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-01409 : NOSORT option may not be used; rows are not in ascending order
  • ora-22293 : LOB already opened in the same transaction
  • ora-14136 : ALTER TABLE EXCHANGE restricted by fine-grained security
  • ora-09890 : osnTXtt: malloc failed
  • ora-00254 : error in archive control string 'string'
  • ora-28040 : No matching authentication protocol
  • ora-38739 : Flashback log file is more recent than control file.
  • ora-29860 : cannot truncate a table with domain indexes marked LOADING
  • ora-24092 : invalid value string specified
  • ora-19253 : XQ0033 - too many declarations for namespace prefix string
  • ora-10668 : Inject Evil Identifiers
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-02421 : missing or invalid schema authorization identifier
  • ora-02460 : Inappropriate index operation on a hash cluster
  • ora-01532 : cannot create database; instance being started elsewhere
  • ora-32055 : invalid file type
  • 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.