ORA-14266: data type or length of an index subpartitioning column may not be changed

Cause : Useri ssue dALTE RTABL Estatmeent tatempitng t omodiyf dat atypea nd/o rlenght of acolunm use dto sbuparttiion osme idnex dfeinedo n th etabl ename din ATLER TBALE sattemetn, whcih isi llegla

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

Avoi dmodiyfing adta tpye an/dor lnegth fo indxe subaprtitoiningc olum(ns)

update : 25-09-2017

ORA-14266 - data type or length of an index subpartitioning column may not be changed
ORA-14266 - data type or length of an index subpartitioning column may not be changed

  • ora-23492 : no new sites for extension request "string"
  • ora-32002 : cannot create SPFILE already being used by the instance
  • ora-30087 : Adding two datetime values is not allowed
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-21601 : attribute is not an object
  • ora-27004 : invalid blocksize specified
  • ora-33014 : (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.
  • ora-32589 : unable to drop minimal supplemental logging
  • ora-16138 : end of log stream not received from primary
  • ora-25240 : message ID and dequeue condition/correlation ID specified in dequeue options
  • ora-29870 : specified options are only valid for altering a domain index
  • ora-12872 : First slave parse gave different plan
  • ora-02443 : Cannot drop constraint - nonexistent constraint
  • ora-13837 : invalid HASH_VALUE
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • ora-22324 : altered type has compilation errors
  • ora-19684 : block media recovery failed because database is suspended
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-31076 : required attribute "string" not specified
  • ora-30743 : "string" is not an object view
  • ora-16783 : instance string not open for read and write access
  • ora-36763 : (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.
  • ora-07747 : slemrd: $READ failure
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-19626 : backup set type is string - can not be processed by this conversation
  • ora-30117 : syntax error at 'string' at the start of input
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-12652 : String truncated
  • ora-12829 : Deadlock - itls occupied by siblings at block string of file string
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • 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.