Re: database link strange behavior

I discovered the source of the strange behavior. There is a parameter called GLOBAL_NAME. This held the previous database name and domain name. I issued: "ALTER DATABASE RENAME GLOBAL_NAME TO TSTU.WORLD ;" I then cycled the instance and the strange behavior went away.

And so it goes.

   James

In article <7fl51u$hh0$1_at_nnrp1.dejanews.com>,   James <james_lorenzen_at_allianzlife.com> wrote:
> I have encountered a puzzling problem regarding database links.
>
> Oracle 7.3.4.3 on AIX 4.3.1 (IBM RS/6000)
>
> global_names = true
>
> We are upgrading Peoplesoft code and part of the process involves code that
> takes the upgraded modules from one database and applies it in another. This
> process uses a database link. Since we are testing teh process, I "cloned"
> the production database from one machine to another. I then renamed the
> database from 'PROD' to 'TSTU' by rebuilding the control file, changing the
> init.ora file and followed guidlines that I found on the "orafaq.org" sight
> for cloning the database.
>
> The listener.ora and tnsnames.ora were adjusted on both machines. When I try
> to use the database link from the upgrade dateabase to test the upgrade, I
> get an Oracle error that my link 'TSTU.WORLD' points to 'PROD.WORLD'. This
> stops the testing (and upgrade) process.
>
> If I set "global_names = false", with no other changes, then the link works
> fine. Obviously I missed something when I cloned 'PROD' to 'TSTU'. My
> question is what was missed. My 'TSTU' database points back to itself when I
> try to link it 'PROD'. This is very confusing. Any help is greatly
> appreciated.
>
> TIA
> James
>
> -----------== Posted via Deja News, The Discussion Network ==----------
> http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Wed Apr 21 1999 - 17:06:17 CDT