ORA-23397: global name "string" does not match database link name "string"

Cause : the datbaase lin kname att he loca lnode dose not macth the golbal nam eof the adtabase htat the ilnk accesses.

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

Ensure htat globla names si set tot rue andt he linkn ame mathces the lgobal naem.

update : 26-05-2017
ORA-23397

ORA-23397 - global name "string" does not match database link name "string"
ORA-23397 - global name "string" does not match database link name "string"

  • ora-01143 : cannot disable media recovery - file string needs media recovery
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-12074 : invalid memory address
  • ora-10654 : Table is of type temporary or external
  • ora-30574 : Cannot create rollback segment in tablespace with AUTO segment space management
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-32629 : measure used for referencing cannot be updated
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-24385 : Application context size or index is not valid
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-14508 : specified VALIDATE INTO table not found
  • ora-09322 : slpdtb: unable to convert packed decimal to binary
  • ora-39169 : Local version of string cannot work with remote version of string.
  • ora-02219 : invalid NEXT storage option value
  • ora-26716 : message limit reached
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-19568 : a device is already allocated to this session
  • ora-12718 : operation requires connection as SYS
  • ora-00275 : media recovery has already been started
  • ora-39307 : operation is illegal without an initial clone
  • ora-29965 : The specified binding does not exist
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-07656 : slsprom:$GETDVI failure
  • ora-31632 : master table "string.string" not found, invalid, or inaccessible
  • ora-12541 : TNS:no listener
  • ora-17510 : Attempt to do i/o beyond file size
  • ora-22951 : NULL returned by ORDER method
  • ora-00165 : migratable distributed autonomous transaction with remote operation is not allowed
  • ora-32739 : Hang analysis aborted due to failed heap re-grow
  • 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.