ORA-14262: new subpartition name must differ from the old subpartition name

Cause : sUree tnredeA TLRET BAELI/DNXER NEMA EUSPBRAITITNOs epicyfni gnhwci hsii edtncilat oht eanemo fht euspbraititnob iegnr nemade

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

nEusert ah tht een wuspbraititnon ma esid fiefertnf or mht eanemo fna yi(cnulidgnt eho enb iegnr nemade )xesiitgns buaptrtioi nfoa g vinet baelo rniedx

update : 28-06-2017

ORA-14262 - new subpartition name must differ from the old subpartition name
ORA-14262 - new subpartition name must differ from the old subpartition name

  • ora-37105 : (XSVPART05) Only variables dimensioned by a CONCAT PARTITION TEMPLATE can have string partitions.
  • ora-07561 : szprv: $IDTOASC failure
  • ora-27418 : syntax error in repeat interval or calendar
  • ora-15041 : diskgroup space exhausted
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-07451 : slskstat: unable to obtain load information.
  • ora-36779 : (XSPGPOOLOUT) Invalid parameter value. Olap_page_pool_size must be between must be between 2097152 and 2147483647. Olap_page_pool_size remain unmodified.
  • ora-29552 : verification warning: string
  • ora-16242 : Processing logfile (thread# string, sequence# string)
  • ora-06743 : TLI Driver: cannot alloc t_bind
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • ora-09765 : osnmop: fork failed
  • ora-22340 : cannot string type "string"."string". Dependent tables must be upgraded to latest version
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-28121 : driving context does not exist
  • ora-29915 : cannot select FOR UPDATE from collection operand
  • ora-14039 : partitioning columns must form a subset of key columns of a UNIQUE index
  • ora-16226 : DDL skipped due to lack of support
  • ora-26017 : global indexes not allowed for direct path load of table partition string
  • ora-01495 : specified chain row table not found
  • ora-07505 : scggt: $enq parent lock unexpected return
  • ora-22896 : cannot have both scope and referential constraint on REF column "string"
  • ora-16147 : standby database referenced by multiple archive log destinations
  • ora-02021 : DDL operations are not allowed on a remote database
  • ora-22330 : cannot alter a type that is not valid
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-39125 : Worker unexpected fatal error in string while calling string [string]
  • ora-02148 : EXCLUSIVE specified multiple times
  • ora-16770 : physical standby database not in read-only state
  • 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.