ORA-22314: method information mismatch in ALTER TYPE

Cause : The number of methods or the method signature do not match that of the original type declaration. This is not supported.

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

Make sure the method signature stay identical for the previously declared method. Do not drop existing methods.

update : 28-07-2017
ORA-22314

ORA-22314 - method information mismatch in ALTER TYPE
ORA-22314 - method information mismatch in ALTER TYPE

  • ora-31182 : Too many PL/SQL DOM handles specified
  • ora-16081 : insufficient number of processes for APPLY
  • ora-28581 : protocol error while executing recursive external procedure
  • ora-09207 : sfsrd: error reading from file
  • ora-08455 : syntax error in CURRENCY SIGN environment clause
  • ora-31656 : cannot use TABLESPACE_EXPR filter with transportable mode
  • ora-24348 : Update or Delete without Where
  • ora-14646 : Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
  • ora-10653 : Table is in a cluster
  • ora-00029 : session is not a user session
  • ora-02145 : missing STORAGE option
  • ora-29263 : HTTP protocol error
  • ora-30928 : Connect by filtering phase runs out of temp tablespace
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-19001 : Invalid storage option specified
  • ora-29974 : Internal event for PL/SQL debugging
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-37044 : (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.
  • ora-01967 : invalid option for CREATE CONTROLFILE
  • ora-01112 : media recovery not started
  • ora-30183 : invalid field width specifier
  • ora-31499 : null value specified for required parameter string
  • ora-13338 : failure in reversing LRS polygon/collection geometry
  • ora-29861 : domain index is marked LOADING/FAILED/UNUSABLE
  • ora-33215 : (CINSERT07) You cannot add session-only values to the workspace object dimension.
  • ora-07260 : spdcr: wait error.
  • ora-02219 : invalid NEXT storage option value
  • ora-28330 : encryption is not allowed for this data type
  • ora-02216 : tablespace name expected
  • ora-16533 : inconsistent Data Guard broker state
  • 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.