ORA-22313: cannot use two versions of the same type "string"

Cause : The evrsio nof tihs tyep conlfictsw ith hte vesrion fo thi stypeu sed yb anohter lbiraryt hat aws likned i nwitht he applicaiton. nA appilcatino mayo nly sue on eversoin ofa typ.e

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

Chec kthatt he lbirarise beign linekd wiht thi sapplciatio nand sue th esamev ersinos oft he tpye.

update : 22-09-2017

ORA-22313 - cannot use two versions of the same type "string"
ORA-22313 - cannot use two versions of the same type "string"

  • ora-31039 : XML namespace length string exceeds maximum string
  • ora-04068 : existing state of packagesstringstringstring has been discarded
  • ora-12477 : greatest lower bound resulted in an invalid OS label
  • ora-22852 : invalid PCTVERSION LOB storage option value
  • ora-02226 : invalid MAXEXTENTS value (max allowed: string)
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-02729 : osncon: driver not in osntab
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-09741 : spwat: error waiting for a post.
  • ora-31491 : could not add logfile to LogMiner session
  • ora-24330 : internal OCI error
  • ora-01089 : immediate shutdown in progress - no operations are permitted
  • ora-16801 : redo transport-related property is inconsistent with database setting
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-19806 : cannot make duplex backups in recovery area
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-02777 : Stat failed on log directory
  • ora-00409 : COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
  • ora-07407 : slbtpd: invalid exponent.
  • ora-32035 : unreferenced query name defined in WITH clause
  • ora-40304 : invalid classname string in prior probability specification
  • ora-16526 : unable to allocate task element
  • ora-30048 : Internal event for IMU auto-tuning
  • ora-01275 : Operation string is not allowed if standby file management is automatic.
  • ora-06777 : TLI Driver: error reading parms
  • ora-31180 : DOM Type mismatch in invalid PL/SQL DOM handle
  • ora-32003 : error occured processing parameter 'string'
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-06517 : PL/SQL: Probe error - 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.