Printable View
I have one instance TCMS in A server and antoher instance TCMS in B server, how do I create the database link in A for B.
It gives me ORA-02082: a loopback database link must have a connection qualifier.
How do you resolve this?? Please help
Thanx, your help is greatly appreciated
Setup a new alias in your tnsnames.ora file on the server and point to the instance on server B.
I have that set up already, this is the entry I have for server B for TCS:
VALLEY=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.10.4.4)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = TCS)
)
)
and this is the one I have for server A for TCS database
TCS =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 1.3.0.45)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = TCS)
)
)
I can connect to both of them otherwise. BUt when I try to create a database link TCS(in server B) in TCS(in server A)
It gives me the above error.
If I try to give Valley as the db link name/db name I get the error:
unable to resolve service name error
Thanx
While you are on serverA, can you sqlplus to serverB using the VALLEY alias?
Yes I can.
What commands are you using to create the DB link?
If you have global_name = true than it is not allowed to create database link different from database global_name.
So, try either change global_Name to valley, or set global_name = false.
Another option is to use fully quilified name , starting with the server name to differentiate between 2 databases.
Global names is set to false in both the servers.
Where do you have this fully qualified name(you mean the service name right) in the server as well as client's machine or.....
Please, publish a command to create db link
CREATE DATABASE LINK TCS
CONNECT TO TCSDATA IDENTIFIED BY tcsdata
USING 'tcs'
/
I get the above mentioned loopback error when I run this.
CREATE DATABASE LINK valley_heart
CONNECT TO TCSDATA IDENTIFIED BY tcsdata
USING 'valley_heart'
/
It creates the db link but when I try to use it:
it gives me unable to resolve service name error.
Why valley_heart, not just valley?
Run this in both databases
select name ,value from v$parameter where name like '%global%';
select * from global_name;
I beleive you will have to change your global name to
tcs.10.10.4.4.
Given global_names=false then the problem is you need to put community in the tname.
Community is in tnsnames.ora and should be the same on both sides. I believe it is usually tcp.world and the entry name would be valley.world=.... not valley=...
Some releases and configurations of SQL*NET could get by without the '.world' everywhere but the tnsnames.ora file.
create the database links using the definitions given to the connect descriptor in the tnsnames.ora file.
create public database link ARC connect to SCOTT identified by tiger using '(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = sridevi)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ARC)
)
)'
sonofsita, your example looked very tempting:D, I tried it but doesn't work gives the same loopback error.
I will try the other options in a little while.
THanx all of you