Re: TNS_ADMIN and OEM

From: Bib Endum <gd-newsgroups_at_spamex.com>
Date: Wed, 18 Feb 2004 13:30:43 -0500
Message-ID: <vbOYb.6472$Cd6.549141_at_news20.bellglobal.com>


"Joop Gijsbers" <jgnospam_at_xs4all.nl> a écrit dans le message de news:40328156$0$576$e4fe514c_at_news.xs4all.nl...
> 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?
>

I have 3 oracle homes on my CLIENT workstation.

I have TNS_ADMIN entries in my registry in:

HKLM->SOFTWARE->ORACLE and
HKLM->SOFTWARE->ORACLE->HOMEn (Where n in (1,2,3))

Maybe more that needed but that solved the problem of having to copy tnsnames.ora and sqlnet.ora on each and every $ORACLE_HOME/network/admin directory. Received on Wed Feb 18 2004 - 19:30:43 CET

Original text of this message