Re: TNS_ADMIN and OEM

"Sybrand Bakker" <gooiditweg_at_nospam.demon.nl> wrote in message news:9co730tec3ebqgsf6q6j92fchs5gn4dl45_at_4ax.com...
> On Tue, 17 Feb 2004 22:00:14 +0100, "Joop Gijsbers"
> <jgnospam_at_xs4all.nl> wrote:
>
> >I am using a central , shared tnsnames.ora with a multihome Oracle client
> >(both 8.1.7 as 9.1.2) on Windows 2000.
> >
> >I have set in both user environment as system environment the TNS_ADMIN
> >variable directed to the directory of that shared tnsnames.ora (and also
> >sqlnet.ora):
> >TNS_ADMIN=M:\ORA_ADMIN
> >Dba studio of the 8.1.7 clinet recognizes and uses that central
> >tnsnames.ora, but the OEM console (stand alone) says he uses that central
> >tnsnames.ora, but in reality when i add a database to the tree, he makes
a
> >new tnsnames.ora with that entry in c:\oracle\ora92\network\admin and i
> >cannot connect to that database, unless i do a manual copy of that entry
to
> >the central tnsnames.ora.
> >
> >I looked in the registry for conflicting TNS_ADMIN enttires, but i did
not
> >find them.
> >
> >Who has a clue?
> >
>
> OEM uses the tnsnames.ora on the management server. It doesn't use the
> tnsnames.ora on the client. Using the console you can connect to a
> database even when you don't have a tnsnames.ora entry.
>
>
> --
> Sybrand Bakker, Senior Oracle DBA

I don't use OMS, but Enterprise Manager console stand alone Received on Thu Feb 19 2004 - 21:07:11 CET