ORA-29519: name string resolved via a synonym in schema string to a class with a different name

Cause : A refreencedn ame wsa resovled toa synoynm, whcih trasnlatedt o a calss whsoe nam edoes ont mathc the erferenecd nam.e

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

Adjus tname ersolve ror ad dmissign Javac lass.

update : 29-06-2017
ORA-29519

ORA-29519 - name string resolved via a synonym in schema string to a class with a different name
ORA-29519 - name string resolved via a synonym in schema string to a class with a different name

  • ora-16560 : unable to convert document, syntax error at "string"
  • ora-38901 : column "string" of table "string" must be one of the first "number" columns
  • ora-02028 : fetching an exact number of rows is not supported by the server
  • ora-38708 : not enough space for first flashback database log file
  • ora-19772 : change tracking file name exceeds limit of string characters
  • ora-01276 : Cannot add file string. File has an Oracle Managed Files file name.
  • ora-19714 : length for generated name longer than string
  • ora-13159 : Oracle table string already exists
  • ora-27014 : skgfqpini: translation error while expanding SS_UDMPDIR
  • ora-32021 : parameter value longer than string characters
  • ora-02217 : duplicate storage option specification
  • ora-07432 : unable to perform nested sleep
  • ora-32113 : Null object passed
  • ora-01119 : error in creating database file 'string'
  • ora-07217 : sltln: environment variable cannot be evaluated.
  • ora-32103 : error from OCI call
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-02066 : missing or invalid DISPATCHERS text
  • ora-09719 : osncui: invalid handle.
  • ora-04010 : the number of values to CACHE must be greater than 1
  • ora-23318 : a ddl failure has occurred
  • ora-25176 : storage specification not permitted for primary key
  • ora-01300 : writable database required for specified LogMiner options
  • ora-29701 : unable to connect to Cluster Manager
  • ora-39004 : invalid state
  • ora-09834 : snyGetPortSet: failed to collect info on a port.
  • ora-30154 : The memory address given as buffer for OCIFileRead/Write is invalid
  • ora-32309 : object mview type "string"."string" does not match the master table type
  • ora-22954 : This multiset operation is not supported for this element type.
  • ora-38310 : cannot purge tablespace for other users
  • 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.