dbTalk Databases Forums  

TNS_ADMIN and OEM

comp.databases.oracle.tools comp.databases.oracle.tools


Discuss TNS_ADMIN and OEM in the comp.databases.oracle.tools forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Joop Gijsbers
 
Posts: n/a

Default TNS_ADMIN and OEM - 02-17-2004 , 03:00 PM






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?



Reply With Quote
  #2  
Old   
Bib Endum
 
Posts: n/a

Default Re: TNS_ADMIN and OEM - 02-18-2004 , 12:30 PM







"Joop Gijsbers" <jgnospam (AT) xs4all (DOT) nl> a écrit dans le message de
news:40328156$0$576$e4fe514c (AT) news (DOT) xs4all.nl...
Quote:
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.




Reply With Quote
  #3  
Old   
Sybrand Bakker
 
Posts: n/a

Default Re: TNS_ADMIN and OEM - 02-18-2004 , 04:06 PM



On Tue, 17 Feb 2004 22:00:14 +0100, "Joop Gijsbers"
<jgnospam (AT) xs4all (DOT) nl> wrote:

Quote:
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


Reply With Quote
  #4  
Old   
Joop Gijsbers
 
Posts: n/a

Default Re: TNS_ADMIN and OEM - 02-19-2004 , 02:07 PM




"Sybrand Bakker" <gooiditweg (AT) nospam (DOT) demon.nl> wrote

Quote:
On Tue, 17 Feb 2004 22:00:14 +0100, "Joop Gijsbers"
jgnospam (AT) xs4all (DOT) 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





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.