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-07-2017
ORA-14402

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

  • ora-12161 : TNS:internal error: partial data received
  • ora-12442 : policy column "string" already used by an existing policy
  • ora-00063 : maximum number of log files exceeded string
  • ora-38104 : Columns referenced in the ON Clause cannot be updated: string
  • ora-23539 : table "string"."string" currently being redefined
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-28104 : input value for string is not valid
  • ora-31667 : parameter name can not be defaulted
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-26079 : file "string" is not part of table string.string
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-16546 : missing or invalid piece
  • ora-06560 : pos, string, is negative or larger than the buffer size, string
  • ora-17507 : I/O request size string is not a multiple of logical block size
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-19706 : invalid SCN
  • ora-02468 : Constant or system variable wrongly specified in expression
  • ora-00024 : logins from more than one process not allowed in single-process mode
  • ora-19696 : control file not found in backup set
  • ora-02771 : Illegal request time out value
  • ora-32147 : Environment not specified
  • ora-02453 : duplicate HASH IS specification
  • ora-16780 : a database has exhausted its archived redo log storage quota
  • ora-15005 : name "string" is already used by an existing alias
  • ora-01164 : MAXLOGFILES may not exceed string
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-08344 : srapp: failed to send redo data to the redo server
  • ora-31030 : Unable to retrieve XML document
  • ora-12845 : failed to receive interinstance parallel execution message
  • ora-28353 : failed to open wallet
  • 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.