ORA-14402: updating partition key column would cause a partition change

Cause : An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition

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

Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key.

update : 22-06-2017

ORA-14402 - updating partition key column would cause a partition change
ORA-14402 - updating partition key column would cause a partition change

  • ora-12229 : TNS:Interchange has no more free connections
  • ora-19594 : control file already included as string
  • ora-25137 : Data value out of range
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-06009 : NETASY: dialogue filename too long
  • ora-24790 : cannot mix OCI_TRANS_RESUME and transaction isolation flags
  • ora-06955 : Number of database servers exceed limit
  • ora-02140 : invalid tablespace name
  • ora-10561 : block type 'string', data object# string
  • ora-39209 : Parameter string requires privileges.
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-02183 : valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-14000 : only one LOCAL clause may be specified
  • ora-07276 : no dba group in /etc/group.
  • ora-19709 : numeric parameter must be non-negative integer
  • ora-19578 : end of volume while duplexing to sequential files, backup piece incomplete
  • ora-23420 : interval must evaluate to a time in the future
  • ora-01623 : log string is current log for instance string (thread string) - cannot drop
  • ora-32586 : multiple specification of a supplemental logging attribute
  • ora-36966 : (XSRELTBL10) workspace object must be a dimension.
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-22162 : element at index [string] has been previously deleted
  • ora-38734 : Flashback log is inconsistent; belongs to another database.
  • ora-01218 : logfile member is not from the same point-in-time
  • ora-31165 : cannot load object-relational XML attribute using direct path
  • ora-39208 : Parameter string is invalid for string jobs.
  • ora-14522 : Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-38101 : Invalid column in the INSERT VALUES Clause: string
  • ora-09310 : sclgt: error freeing latch
  • 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.