Re: problems with the names of dblinks

Have a look at your GLOBAL_NAMES parameter setting - I think you will find that it is set to TRUE. This forces the db link to have the same name as the database you are connecting to.

Set this to FALSE and your problems should go away.

Look at the Oracle Server Reference and Oracle Server Administration Guide for more details and the reasoning for the setting to TRUE. Used in a distributed environment to force unique database names.

Regards
--
Kevin A Lewis (BOCM PAULS LTD - Animal Feed Manufacturer - Ipswich England)

                        <KevinALewis_at_HotMail.com>

The views expressed herein by the author of this document are not necessarily those of BOCM PAULS Ltd. Van <poppop_at_ole.com> wrote in message news:7or40f$fgs$1_at_diana.bcn.ttd.net...
> We have two machines running different instances of Oracle. One is a NT
> running Oracle 8.0.5.0.0 and the other is a Sun running Oracle 8.0.4.0.0.
>
> The NT machine is called BACUS. His db_name is 'SGI' and his db_domain
> 'WORLD'.
>
> The Sun machine is called AKIRA. His db_name is 'SIG' and his db_domain
> 'WORLD'.
>
> We want to create a dblink from BACUS to AKIRA named 'akira'. We want to
do
> "select sysdate from dual_at_akira", for example.
>
> We also have defined 'BACUS' in the TNSNAMES.ORA file like this
>
> BACUS.WORLD =
> (DESCRIPTION =
> (ADDRESS = (PROTOCOL = TCP)(HOST = 13.291.322.234)(PORT = 1521))
> (CONNECT_DATA = (SID = SGI))
> )
>
> If we try to do it with the sentence:
>
> CREATE PUBLIC DATABASE LINK BACUS CONNECT TO JARL IDENTIFIED BY MYPASSWD
> USING 'BACUS';
>
> and we try the sentence
>
> select sysdate from dual_at_bacus;
>
> we receive the following error:
>
> Ora-02085: Database link BACUS.WORLD connects to SGI.WORLD
>
> If we try to name the databaselink "SGI" instead of "BACUS" and we try
> select sysdate from dual_at_SGI;
> it works well!
>
> But we don't want this name. We wan't to call it "BACUS".
>
> Any ideas?
>
> Thank you!
>
>
>
Received on Fri Aug 13 1999 - 05:14:56 CDT