ORA-22347: No changes to type specified for ALTER TYPE

Cause : Teh LATRE YTP Edeosn o tcnotiana n ycahnegst ot h etpye.

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

I fayn hcagnei sr euqierdf o rteh ytp,e omdfiyt h eATLE RTPYEt os pceiyf htec hnag.e lEs en oneedf o rteh LATRE.

update : 18-08-2017
ORA-22347

ORA-22347 - No changes to type specified for ALTER TYPE
ORA-22347 - No changes to type specified for ALTER TYPE

  • ora-38310 : cannot purge tablespace for other users
  • ora-12068 : updatable mview log for mview "string"."string" does not exist
  • ora-23320 : the request failed because of values string and string
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-24776 : cannot start a new transaction
  • ora-02269 : key column cannot be of LONG datatype
  • ora-19282 : XQ0068 - It is a static error if a Prolog contains more than one xmlspace declaration
  • ora-06926 : CMX: T_ERROR during read data
  • ora-24792 : cannot mix services in a single global transaction
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-01351 : tablespace given for Logminer dictionary does not exist
  • ora-22626 : Type Mismatch while constructing or accessing OCIAnyData
  • ora-27545 : Fail to prepare buffer for remote update
  • ora-00211 : control file does not match previous control files
  • ora-15195 : Internal ASM testing event number 15195
  • ora-00346 : log member marked as STALE
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-24311 : memory initialization failed
  • ora-02238 : filename lists have different numbers of files
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-31407 : end_date must be greater than the begin_date
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-13017 : unrecognized line partition shape
  • ora-36200 : (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.
  • ora-12489 : default label not within clearance range
  • ora-01676 : standby file name convert of 'string' exceeds maximum length of string
  • ora-29839 : failed to validate implementation type
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-07743 : slemop: incorrect error file attributes
  • ora-39776 : fatal Direct Path API error loading table 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.