ORA-14061: data type or length of an index partitioning column may not be changed

Cause : Usre issue dALETR ATBL Esttaemnet tatepmtign t omoidfyd at atyep adn/o rlegntho f acoulmnu se dtop arittino smoe nide xdeifne dont het abel nmaedi n LATE RTALBE tsatmeen,t wihchi s lileagl

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

Aviod omdiyfin gdaat tpye nad/ro lnegt hofi ndxe pratiitonnig oclunm(s)

update : 26-06-2017

ORA-14061 - data type or length of an index partitioning column may not be changed
ORA-14061 - data type or length of an index partitioning column may not be changed

  • ora-09797 : Failed to get O/S MAC privileges.
  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-33445 : (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
  • ora-00215 : must be at least one control file
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-12414 : internal LBAC error: string Error: string
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-14631 : the partition bounds do not match the subpartition bounds of the partition
  • ora-27041 : unable to open file
  • ora-19243 : XQ0023 - invalid document node content in element constructor
  • ora-36881 : (XSSRF00) The OLAP DML ROW2CELL function can only be used in a LIMITMAP.
  • ora-23350 : maximum number of recursive calls exceeded
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-38306 : this object is not recoverable standalone
  • ora-29553 : class in use: string.string
  • ora-01562 : failed to extend rollback segment number string
  • ora-24192 : the property name cannot be null
  • ora-06140 : NETTCP: no such user
  • ora-27050 : function called with invalid FIB/IOV structure
  • ora-29807 : specified operator does not exist
  • ora-19765 : mount id string does not match mount id string in control file
  • ora-31445 : invalid lock handle while acquiring lock on string
  • ora-00122 : cannot initialize network configuration
  • ora-16212 : number processes specified for APPLY is too great
  • ora-01355 : logminer tablespace change in progress
  • ora-22979 : cannot INSERT object view REF or user-defined REF
  • ora-13354 : incorrect offset in ELEM_INFO_ARRAY
  • ora-38424 : no attribute set currently assigned to the expression set
  • ora-01685 : max # extents (string) reached in index string.string partition 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.