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 : 26-07-2017

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

  • ora-01159 : file is not from same database as previous files - wrong database id
  • ora-24386 : statement/server handle is in use when being freed
  • ora-30976 : invalid Parent Order Key Index option for XML Index
  • ora-08269 : destroy_ora_addr: cannot destroy name
  • ora-28132 : Merge into syntax does not support security policies.
  • ora-30000 : missing either trim specification or char expression in TRIM
  • ora-12492 : DBLOW cannot be changed
  • ora-26060 : Can not convert type identifier for column string
  • ora-29813 : non-supported object type with associate statement
  • ora-07253 : spdes: semctl error, unable to destroy semaphore set.
  • ora-28356 : invalid open wallet syntax
  • ora-29553 : class in use: string.string
  • ora-27006 : sbtremove returned error
  • ora-08121 : Number of indexes need to be maintained offline exceeds limit for DML
  • ora-16660 : FSFO operation attempted in absence of a broker configuration
  • ora-31151 : Cyclic definition encountered for string: "string"
  • ora-09878 : sstascre/sstasat: shmat error, unable to attach tas write page
  • ora-38749 : A media recovery has been started.
  • ora-32055 : invalid file type
  • ora-23614 : Script string does not exist
  • ora-01881 : timezone region id number is invalid
  • ora-13386 : commit/rollback operation error: [string]
  • ora-01113 : file string needs media recovery
  • ora-01135 : file string accessed for DML/query is offline
  • ora-36712 : (XSMXALLOC02) Relation workspace object must be a one-dimensional self-relation to be used as a SOURCE or BASIS with ALLOCATE.
  • ora-12663 : Services required by client not available on the server
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • ora-37036 : (XSMLTDCL02) You cannot DELETE objects in analytic workspace string because it is attached in MULTI mode.
  • ora-06914 : CMX: unexepected event during start of oracle
  • ora-26674 : Column mismatch in 'string.string' (LCR: string type=string; DB: string type=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.