Re: OEM 2.1 discovering nodes incorrectly
From: Van Messner <vmessnerNOvmSPAM_at_discovernet.com.invalid>
Date: 2000/07/13
Message-ID: <03680e20.333bed3d_at_usw-ex0106-046.remarq.com>#1/1
Date: 2000/07/13
Message-ID: <03680e20.333bed3d_at_usw-ex0106-046.remarq.com>#1/1
OEM can have connection problems. Here is one thing you can try.
Let's say you OEM manger is named SYSMAN. If you go to the
SYSMAN table SMP_VDN_TARGET_LIST you will see information about
the discovered nodes. There is a column called TNSADDR where you
may see a problem with your connect string.
Also, SIDs are more reliable than service names in your OEM
tnsnames.ora file. If you have a choice I would stick with SIDs
for now.
Finally adding the period almost makes it seem as if OEM thinks
your names_default_domain in sqlnet.ora consists of one or more
blank spaces.
Van
Got questions? Get answers over the phone at Keen.com.
Up to 100 minutes free!
http://www.keen.com
Received on Thu Jul 13 2000 - 00:00:00 CEST