ORA-02374: conversion error loading table string.string

Cause : Ar o wcuol dnto eb olaeddi not htet albeb eacues hteer awsa ocnevriso nerro rfro noeo rm oer oclmun si nar o.w

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

See htem essaeg hta tflolwosf o rmroei noframtoina buott h erwo hta tcuol dnto eb olaedd .T oaovi dtihse rorr ,mkaes uer hted eifntiino fo htet albeb enigi mopretdm acthse hted eifntiino fo htet albeb enige xopretd.

update : 27-04-2017
ORA-02374

ORA-02374 - conversion error loading table string.string
ORA-02374 - conversion error loading table string.string

  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-37142 : (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
  • ora-31109 : Action failed as parent resource string is locked
  • ora-01917 : user or role 'string' does not exist
  • ora-02807 : Allocation of memory for I/O vectors failed.
  • ora-39315 : call to DBMS_SCHEMA_COPY.SWAP is not legal
  • ora-30355 : materialized view container does not exist
  • ora-32619 : incorrect use of MODEL ITERATION_NUMBER
  • ora-13064 : relationship information table has inconsistent data for feature table [string]
  • ora-15017 : diskgroup "string" cannot be mounted
  • ora-16257 : Switchover initiated stop apply successfully completed
  • ora-28538 : result set not found
  • ora-19212 : no key columns specified before call to DBMS_XMLSTORE.updateXML()
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-06432 : ssaio: Buffer Not Aligned
  • ora-24159 : invalid variable definiton
  • ora-10583 : Can not recovery file string renamed as missing during test recovery
  • ora-09709 : soacon: failed to accept a connection.
  • ora-02440 : Create as select with referential constraints not allowed
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-01904 : DATAFILE keyword expected
  • ora-02470 : TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
  • ora-25145 : allocation policy already specified
  • ora-34360 : (MXDSS15) number other users writing
  • ora-22633 : Error freeing AnyDataSet
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-16052 : DB_UNIQUE_NAME attribute is required
  • ora-19261 : XQ0041 - non empty URI in QName
  • ora-25330 : PL/SQL associative arrays may not be used with AQ array operations
  • 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.