Re: OEM 2.1 discovering nodes incorrectly

1. Your SQLNET.ORA file may tell your system to use HOSTNAMES. NAMES.DIRECTORY_PATH=(HOSTNAMES) to use tnsnames.ora set it to NAMES.DIRECTORY_PATH=(TNSNAMES)
2. OEM 21 has a problem truncating the tnsnames.ora file. There are patches on Metalink to fix this.
3. If using the TNS_ADMIN variable to point to the directory where tnsnames.ora is, there is a note about 8.1 needing the trailing backslash in the value for it to work. . . c:\oracle\network\, not c:\oracle\network
4. For discovery to work properly, the node being discovered needs to have had the listener 'dbsnmp_start' executed. This is what OEM communicates with to gather connection information. On Unix 'lsnrctl dbsnmp_status<return>'. node = machine name, not instance name.
5. Credentials should be set in the 'console' 'preferences' screen, then they become default for the instance.

HTH
Ted

"Verna Legaspi" <verna.legaspi_at_attws.com> wrote in message news: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 Thu Jul 13 2000 - 00:00:00 CEST