When I run "agentctl start agent" on our Oracle 9 installation,
nmiconf.log complains with:

Warning : No Listener found for SID db1. db1 will be skipped

where db1 is the SID name. This happens for all databases on the
server so that snmp_ro.ora shows:

snmp.visibleservices = ()

Why?

I read the Intelligent Agent User Guide and the section about auto
discovery on Unix. I can confirm that oratab lives in /var/opt/oracle
and that listener.ora lives in $ORACLE_HOME/network/admin.

Thanks,

--
Sean Kelly

if you don't have access to metalink here is the note:

This worked for me when I had the same exact problem:

Environment:
Oracle Intelligent Agent
Microsoft Windows NT
Microsoft Windows 2000

Symptom:
You have discovered a node from the EM console, but cannot see the databases.

The Agent's %ORACLE_HOME%/network/log/nmiconf.log shows:

Warning : Listener <LISTENER_name> defined in <path>\listener.ora
will be skipped because it does not have a corresponding NT service entry
Warning : Skipping Oracle<Oracle_Home>TNSListener :
Could not find corresponding listener definition in (<path>\listener.ora)
Warning : No Listener found for SID <SID__name>. <SID_name> will be skipped

Cause:
When the Agent process starts, a script is executed to locate manageable
services on the node. The script is called nmiconf.tcl and is the primary
script for discovering databases and listeners on the server.

The new universal Installer checks for an ORACLE_HOME_NAME and an
ORACLE_HOME_PATH, both of which get stored in the registry. The new service
name is created using the ORACLE_HOME_NAME as part of the service name which
is the text portion of the service name, between 'Oracle' and 'TNSListener'.

During the execution of "nmiconf.tcl" script, the
'proc nmiconf_getListenerOraFileVersion' uses the version portion of the
service to compare against the path name to determine if they are the same
version; since they're not, this procedure returns a 'bad' version.

Therefore, the 'proc nmiconf_findListenerNTService' fails the version
comparison, causing the error to be given and the Listener to be ignored.


Fix:

NOTE: Before beginning this workaround, please make a backup copy of the
nmiconf.tcl script.

1. Modify the nmiconf.tcl script and find the line that includes:

proc nmiconf_findListenerNTService

2. Then comment out the entry under the above heading that includes:

set isVersionEqual [string compare $version [lindex $listenerNTServiceDeta...etc

3. Then add the following line right after the above commented line:

set isVersionEqual 0

4. Save and Close the nmiconf.tcl script

5. Restart the Intelligent Agent

6. Refresh the Node from within the EM Console

groups (AT) shortestpath (DOT) org (Sean) wrote in message news:<f2bf2411.0310170408.505984f0 (AT) posting (DOT) google.com>...