Re: Database link and global names

If you rename global_names from FALSE to TRUE.you will almost definitely have to recreate all your database links unless your DBA was extremely correct when he initially created them.
I have global_names set to true on my database. I access remote databases in all sort of states, I used the following,

Log on to the remote database that you want to connect to, run
 select * from global_name
/
  on the remote database. This should return the "global_name" of the "remote" database,
use this as the database link name.
e.g.
oraglob.world
In order to identify a particular user/database link you could append an identifier
so the link for Scott could become oraglob.world_at_scott

George Barbour.

"Martin Drautzburg" <martin.drautzburg_at_web.de> wrote in message news:87adqk2fpv.fsf_at_web.de...
> After a migration from 8.0.5 to 8.1.7 we ran into the following
> problem:
>
> On the database "foo.world" there used to be a database link "bar"
> pointing to a database "bar". Global names had been set to true
> because we used advanced replication.
>
> foo.world -bar-----> bar
>
> After the migration the "bar" database link magically appeared as
> "bar.world". Now I have a link named "bar.world" pointing to a
> database named "bar". This does not work with global names = true.
>
> foo.world -bar.world--> bar
>
> Neither me nor oracle support could figure out be how to establish a
> database link from a database "with a domainname" to a database
> "without a domainname" when global names = true.
>
> Of course I could rename bar to bar.world, but this this database is
> not under our control and the guys there will claim that nothing has
> changed on their side.
>
> I might also change foo.world to foo, but this is a node in a
> replicated environment and I'd have to change dozens of database
> names or *they* would run into a global names problem.
>
> For any help on this issue I'd be most grateful.
>
>
Received on Thu May 30 2002 - 05:00:39 CDT