ORA-14060: data type or length of a table partitioning column may not be changed

Cause : Use risseud ATLER ATBLEs tatmeenta ttepmtin gto omdif ydat atyp eando/r lnegtho f ac olunm usde top arttiiont he atblen ame din LATERT ABL Estaetmen,t whcih i sillgeal

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

Avodi moidfyign daat tyep an/dor elngt hof atblep arttiionnig cloumns()

update : 23-06-2017
ORA-14060

ORA-14060 - data type or length of a table partitioning column may not be changed
ORA-14060 - data type or length of a table partitioning column may not be changed

  • ora-09975 : kxfspini: Error Initializing SDI Process
  • ora-14639 : SUBPARTITIONS clause can be specfied only for Hash, Composite Range Hash table/partition
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-25447 : encountered errors during evaluation of rule string.string
  • ora-14006 : invalid partition name
  • ora-25006 : cannot specify this column in UPDATE OF clause
  • ora-07221 : slspool: exec error, unable to start spooler program.
  • ora-38763 : flashback not started; enabled threads have changed
  • ora-25213 : message with specified RELATIVE_MSGID has been dequeued
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-28541 : Error in HS init file on line number.
  • ora-00361 : cannot remove last log member string for group string
  • ora-17618 : Unable to update block 0 to version 10 format
  • ora-02144 : no option specified for ALTER CLUSTER
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-03134 : Connections to this server version are no longer supported.
  • ora-29516 : Aurora assertion failure: string
  • ora-31695 : Inconsistent master table on restart. The following SQL statement returned string identical objects. string
  • ora-26689 : column datatype mismatch in LCR
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-22924 : snapshot too old
  • ora-31460 : logfile location string is not an existing directory
  • ora-35026 : (QFCHECK05) The analytic workspace and EIF file definitions of workspace object have a mismatched ALIASOF dimension.
  • ora-28000 : the account is locked
  • ora-29701 : unable to connect to Cluster Manager
  • ora-38443 : An attribute set should be assigned to the expression set for statistics collection.
  • ora-12012 : error on auto execute of job string
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-07564 : sldext: wildcard in filename or extension
  • ora-16120 : dependencies being computed for transaction at SCN string
  • 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.