// *Cause: a database link connected to a database with a different name.
// The connection is rejected.
// *Action: create a database link with the same name as the database it
// connects to, or set global_names=false.
Also, I would suggest , try establishing a normal connection and make sure that your connection is perfect. Then, check your database nameing convention and make sure you have done it correctly.
[QUOTE][i]Originally posted by m_d_marian [/i]
[B]If you want to use global_names=true for another purposes,
the name of your link [dw_link] must match the name of the USING 'ORCL', so name the link with thee exact USING string(ORCL). [/B][/QUOTE]
No, it is a litle bit different. If GLOBAL_NAMES=TRUE, what has to be the same as the remote database name is the *db link name*, not what you specify in the USING part of the db link creation command.
So if global name of your remote database is "ORCL.acme.com", and your local db server tnsnames.ora entry for that remote database is named "REMOTE_DB", your create db link command should be:
CREATE DATABASE LINK orcl.acme.com CONNECT TO user_a IDENTIFIED BY pwd_a USING 'remote_db';
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?