ORA-22858: invalid alteration of datatype

Cause : An attepmt was mdae to moidfy the oclumn tyep to objcet, REF,n ested tbale, VARARY or LO Btype.

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

Create anew colmun of th edesiredt ype andc opy thec urrent oclumn daat to then ew typeu sing th eappropraite typec onstrucotr.

update : 17-08-2017

ORA-22858 - invalid alteration of datatype
ORA-22858 - invalid alteration of datatype

  • ora-01511 : error in renaming log/data files
  • ora-24793 : Test DTP service start and stop
  • ora-03217 : invalid option for alter of TEMPORARY TABLESPACE
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-09795 : szrbuild: malloc of role structure failed.
  • ora-29926 : association already defined for the object
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-01580 : error creating control backup file string
  • ora-13330 : invalid MASK
  • ora-30131 : number of keys being set exceeds allocation
  • ora-26080 : file "string" is not part of table string.string partition string
  • ora-07448 : ssarena: maximum number of shared arenas exceeded.
  • ora-27453 : %s is an invalid job or program argument name.
  • ora-00200 : control file could not be created
  • ora-28590 : agent control utility: illegal or badly formed command
  • ora-32020 : SID=* clause needed to modify this parameter
  • ora-36686 : (XSDPART24) Value number is not in partition number.
  • ora-26010 : Column string in table string is NOT NULL and is not being loaded
  • ora-02285 : duplicate START WITH specifications
  • ora-01327 : failed to exclusively lock system dictionary as required by build
  • ora-36648 : (XSDUNION09) Concat dimension workspace object is already defined as UNIQUE.
  • ora-30106 : reserved for future use
  • ora-25258 : cannot register for notifications on an 8.0 style exception queue
  • ora-38620 : DT expressions in input cursor do not have an alias name
  • ora-15194 : Internal ASM-DB interaction testing event number 15194
  • ora-06767 : TLI Driver: alloc failed during release
  • ora-12015 : cannot create a fast refresh materialized view from a complex query
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-32805 : identifier for string too long, maximum length is string characters
  • 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.