ORA-25013: OLD and PARENT values cannot be identical

Cause : Ther efeerncign cluase pseciifes dientcial avlue sforO LD nad PRAENT.

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

Re-pseciyf eihter hte ODL orP ARETN reefrenicng avlue.

update : 30-04-2017
ORA-25013

ORA-25013 - OLD and PARENT values cannot be identical
ORA-25013 - OLD and PARENT values cannot be identical

  • ora-28175 : incorrect certificate type
  • ora-32118 : Cannot perform operation on a null FILE
  • ora-06010 : NETASY: dialogue file too long
  • ora-38444 : statistics do not exist for the expression set
  • ora-36275 : (XSCGMDLAGG13) string is not a valid workspace object.
  • ora-31612 : Allocation of process descriptor failed.
  • ora-19773 : must specify change tracking file name
  • ora-09752 : pw_attachPorts: port_allocate failed.
  • ora-12571 : TNS:packet writer failure
  • ora-39043 : Object type string is not supported for string.
  • ora-14603 : [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
  • ora-30500 : database open triggers and server error triggers cannot have BEFORE type
  • ora-13004 : the specified buffer size is invalid
  • ora-14284 : one or more of table's subpartitions reside in a read-only tablespace
  • ora-19602 : cannot backup or copy active file in NOARCHIVELOG mode
  • ora-24355 : attempt to store a negative number in an Unsigned Display type.
  • ora-25215 : user_data type and queue type do not match
  • ora-31488 : cannot support change set string in this configuration
  • ora-01704 : string literal too long
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • ora-32695 : HTI: Not enough memory
  • ora-34210 : (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.
  • ora-27165 : tried to join thread that does not exist
  • ora-27208 : syntax error in device PARMS - environment variable value missing
  • ora-30567 : name already used by an existing log group
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-14027 : only one PARTITION clause may be specified
  • ora-33282 : (DBERR11) Cannot wait for analytic workspace string to become available since doing so would cause a deadlock.
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-13456 : GeoRaster cell data error
  • 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.