Why valley_heart, not just valley?
Printable View
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