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 : 17-08-2017

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-30555 : global index partitioning key is an expression
  • ora-06109 : NETTCP: message receive failure
  • ora-27073 : Trying to close a file which has async I/Os pending to be dequeued
  • ora-06026 : NETASY: port close failure
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • ora-25303 : Buffered operation allowed only on the owner instance
  • ora-30055 : NULL snapshot expression not allowed here
  • ora-31413 : change set string is currently being advanced
  • ora-38603 : FI including & excluding cursor can only return one column
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-12705 : Cannot access NLS data files or invalid environment specified
  • ora-01591 : lock held by in-doubt distributed transaction string
  • ora-00063 : maximum number of log files exceeded string
  • ora-19718 : length for command id longer than string
  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-29311 : export dump file was not generated by this database, string does not match
  • ora-24065 : propagation for QUEUE string and DESTINATION string already disabled
  • ora-39025 : jobs of type string are not restartable
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-31502 : invalid number supplied for supplemental_processes
  • ora-12035 : could not use materialized view log on "string"."string"
  • ora-31469 : cannot enable Change Data Capture for change set string
  • ora-30158 : The OCIFileWrite causes the file to exceed the maximum allowed size
  • ora-31475 : redo log catalog contains no metadata for the source table
  • ora-36376 : (XSAGZERO) AGGREGATE attempted to divide by zero. Set DIVIDEBYZERO to YES if you want NA to be returned as the result of a division by zero.
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-12519 : TNS:no appropriate service handler found
  • ora-30358 : summary and materialized view are not in same schema
  • ora-14508 : specified VALIDATE INTO table not found
  • 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.