ORA-23398: user name "string" at database link "string" does not match local user name "string"

Cause : teh sue rnmaeo ft h erpelciaito namdiinsrtaito nuesra tt h elcoa lndoea n dteh sue rnmaea tt h endoec orrepsodnign ot hted aatbsael ikn raen o tteh asm.e ySmemtircr elpiactoine xepcst htet w ouesr st ob eteh asm.e

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

Esnuer hta tteh sue rI Do fteh erpilctaino damniitsrtaino sue ra tteh olcla ond eadn hteu sre DI ta hten oed ocrersopnidn gt oteh adtbaaes iln kaer htes aem.

update : 25-06-2017

ORA-23398 - user name "string" at database link "string" does not match local user name "string"
ORA-23398 - user name "string" at database link "string" does not match local user name "string"

  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-03126 : network driver does not support non-blocking operations
  • ora-36698 : (XSRELTBL03) QDR dimension workspace object should be in the dimension list that dimensions the relation.
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-08180 : no snapshot found based on specified time
  • ora-07223 : slspool: fork error, unable to spawn spool process.
  • ora-16742 : the standby database "string" has exhausted its quota
  • ora-16756 : resource guard could not open standby database read-only
  • ora-14611 : Duplicate subpartition name string in template
  • ora-13761 : invalid filter
  • ora-24369 : required callbacks not registered for one or more bind handles
  • ora-25237 : navigation option used out of sequence
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-38733 : Physical size string less than needed string.
  • ora-35952 : (XSSPFC01) The string dimension workspace object and the string dimension workspace object must have the same number of values in status for SPFCEXEC method number.
  • ora-13270 : OCI error string
  • ora-16826 : apply service state is inconsistent with the DelayMins property
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-19005 : Duplicate XMLType LOB storage option
  • ora-07407 : slbtpd: invalid exponent.
  • ora-09275 : CONNECT INTERNAL is not a valid DBA connection
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-25532 : MTTR specified is too large: string
  • ora-39953 : the range value specified is beyond allowed range
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-35280 : (SNSYN165) The format of the AGGREGATE command is: AGGREGATE varname1 [varname2 varname3 ...] USING aggmap-name [COUNTVAR intvar-name1 [intvar-name2 intvar-name3 ...]] [FUNCDATA] [THREADS #]
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • 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.