Title: RE: ??? strange database link problem
Check out the global_name init.ora parameter.
It is probably set to true, which forces the name of the
database link to be the same as the alias.
R. Matt Adams - GE Appliances - [EMAIL PROTECTED]
Meddle not in the affairs of troff
Title: RE: ??? strange database link problem
Check
NAMES.DEFAULT_DOMAIN in
sqlnet.ora
Regards
Ivo
Libal
-Original Message-From: Adams, Matthew (GEA, 088130)
[mailto:[EMAIL PROTECTED]]Sent: Thursday, May 17, 2001 03:55
PMTo: Multiple recipients of list ORACLE-LSubject: RE
The parameter is the same on both servers. I changed the link name from
instance_link to instance and it worked fine. Why is it
complaining about the _link in the name?
Ron
-Original Message-
Sent: Thursday, May 17, 2001 9:41 AM
To: Multiple recipients of list ORACLE-L
Check
Title: RE: ??? strange database link problem
# Global Naming -- enforce that a dblink has same
name as the db it connects toglobal_names = true
Your problem is this.
make it to false or obey the rules.
- Original Message -
From:
Libal, Ivo
To: Multiple recipients of list
That was it.
Thanks!
-Original Message-
Sent: Thursday, May 17, 2001 10:31 AM
To: Multiple recipients of list ORACLE-L
# Global Naming -- enforce that a dblink has same name as the db it connects
to
global_names = true
Your problem is this.
make it to false or obey the rules.
hi andrea,
create using connect_data as in Tnsnames.ora.
create database link test connect iccssowner indentified by icssowner
using '(DESCRIPTION = (ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(Host =
XYZ)(Port = 1521))
)(CONNECT_DATA = (SID = ORCL)))'
then test...
select sysdate from
Andrea,
When GLOBAL_NAMES=TRUE then the name of the db link
must match the global name of the db to which it
connects. You can check the global_name with
SELECT * FROM GLOBAL_NAME;
In your case the global_name of the remote db is
AU34TD.WORLD so you will get this error unless you
name the db
