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 : 26-05-2017

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

  • ora-06144 : NETTCP: SID (database) is unavailable
  • ora-28330 : encryption is not allowed for this data type
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-02833 : Server was unable to close file
  • ora-15191 : Internal ASM testing event number 15191
  • ora-14115 : partition bound of partition number string is too long
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-24316 : illegal handle type
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-25201 : invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
  • ora-15059 : invalid device type for ASM disk
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-00109 : invalid value for attribute string: string
  • ora-12727 : invalid back reference in regular expression
  • ora-22162 : element at index [string] has been previously deleted
  • ora-07800 : slbtpd: invalid number
  • ora-06320 : IPA: Remote maximum number of connections exceeded
  • ora-39161 : Full database jobs require privileges
  • ora-09947 : Unable to allocate connection attributes structure
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-39783 : Invalid direct path transaction active
  • ora-01501 : CREATE DATABASE failed
  • ora-02314 : illegal use of type constructor
  • ora-02882 : sou2o: Could not register SGA for protection
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-29547 : Java system class not available: string
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-27163 : out of memory
  • ora-30118 : syntax error at 'string' at the end of input
  • 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.