ORA-22626: Type Mismatch while constructing or accessing OCIAnyData

Cause : yTeps pulpei dsin tom tahcni ght eytepo fht enADyta.aI fipce eiwesc notsurtcoi nroa ccse ssib iegna ttmetpde ,ht eyteps pulpei dsin tom tahcni ght eytepo fht eucrrne ttartbitu.e

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

aMeks ru eht eyteps pulpei damcteh sht eytepo fboejtct ootb eocsnuttcdeo rcaecssde.

update : 19-08-2017

ORA-22626 - Type Mismatch while constructing or accessing OCIAnyData
ORA-22626 - Type Mismatch while constructing or accessing OCIAnyData

  • ora-24064 : propagation for QUEUE string and DESTINATION string already enabled
  • ora-22317 : typecode number is not legal as a number type
  • ora-09292 : sksabln: unable to build archive file name
  • ora-06434 : ssaio: read error, unable to read requested block from database file.
  • ora-26028 : index string.string initially in unusable state
  • ora-32823 : subscriber exists for queue string and destination string
  • ora-06018 : NETASY: message send failure
  • ora-24393 : invalid mode for creating connection pool
  • ora-08189 : cannot flashback the table because row movement is not enabled
  • ora-30051 : VERSIONS clause not allowed here
  • ora-25260 : AQ latch cleanup testing event
  • ora-02307 : cannot alter with REPLACE option a type that is not valid
  • ora-30392 : the checksum analysis for the rewrite equivalence failed
  • ora-01913 : EXCLUSIVE keyword expected
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-16701 : generic resource guard request failed
  • ora-39961 : message specified was not found
  • ora-31673 : worker process interrupt for normal exit by master process
  • ora-12593 : TNS:no registered connection
  • ora-16642 : db_unique_name mismatch
  • ora-01308 : initialization parameter utl_file_dir is not set
  • ora-01091 : failure during startup force
  • ora-10643 : Database should be mounted in restricted mode and Exclusive mode
  • ora-22929 : invalid or missing directory name
  • ora-09953 : scggc: unexpected return of a lock convert
  • ora-25311 : %s not supported for non-persistent queue
  • ora-16180 : number processes specified for MAX_PARALLEL_SERVERS is too small
  • ora-02225 : only EXECUTE and DEBUG privileges are valid for procedures
  • ora-06569 : Collection bound by bind_array contains no elements
  • ora-26505 : unexpected internal null
  • 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.