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 : 26-04-2017
ORA-22314

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

  • ora-12218 : TNS:unacceptable network configuration data
  • ora-07237 : slemcl: invalid file handle, seals do not match.
  • ora-25247 : %s is not a recipient of specified message
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-24122 : invalid block range specification
  • ora-31441 : table is not a change table
  • ora-16541 : site is not enabled
  • ora-06316 : IPA: Invalid database SID
  • ora-31434 : purge is currently running
  • ora-30767 : OID type mismatch
  • ora-31450 : invalid value for change_table_name
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-00073 : command string takes between string and string argument(s)
  • ora-38311 : cannot purge objects owned by other users
  • ora-19922 : there is no parent row with id string and level string
  • ora-24357 : internal error while converting from to OCIDate.
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-12557 : TNS:protocol adapter not loadable
  • ora-38794 : Flashback target time not in current incarnation
  • ora-25127 : RELY not allowed in NOT NULL constraint
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-19711 : cannot use reNormalizeAllFileNames while database is open
  • ora-27102 : out of memory
  • ora-16746 : resource guard encountered errors during database mount
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-01373 : insufficient memory for staging persistent LogMiner session
  • ora-06303 : IPA: Message send error
  • ora-02290 : check constraint (string.string) violated
  • ora-36212 : (XSAGOP06) In AGGMAP workspace object, you can only specify the MIN, MAX, FLOOR, and CEILING arguments while using the PROPORTIONAL operator, not string.
  • ora-01571 : redo version string incompatible with ORACLE version 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.