Re: OEM 2.1 discovering nodes incorrectly

Verna,
Usually when the agent discovers the db service incorrectly, there is a GLOBAL_DBNAME parameter in the listener. That is the how the agent will discover the database (if the parameter is used). Many times, this parameter is set to the host name of the machine.

Verna Legaspi wrote in message <8kkpp2$7bl$1_at_redftp.redftp.attws.com>...
>Hello,
>
>I'm trying to use the extra management packs of OEM 2.1 (tuning,
>diagnostics, etc.)
>
>I'm assuming my problem is the discovery process picks up slightly
 incorrect
>information about my nodes/databases. It tries to connect using the host
>name instead of the net8/local net services name. It also adds a period
 (.)
>to the host name. So, whenever I try to connect to any of these nodes, I
>get an error:
>
>Error occurred on <host>. while connecting to target database:
>
>XP-21161: Database connection attempt has failed
>
>ORA-12564: TNS:connection refused
>
>The programs I would like to use (SQL Analyze, Change Manager) are picky as
>to what type of nodes they will let you connect to. They will only connect
>to automatically discovered nodes, therefore I cannot manually edit the
>"Service:" field on my Database Login dialog box.
>
>Anyone run across this before or have any ideas?
>
>TIA,
>Verna
>
>
>
Received on Mon Jul 17 2000 - 00:00:00 CEST