problem with dbsnmp agent on Solaris

From: Ed Stevens <nospam_at_noway.nohow>
Date: Wed, 19 Feb 2003 10:46:05 -0600
Message-ID: <42c75v42srboct5ltpffhddipth45rq42a@4ax.com>

Platform: Oracle 8.1.7.0.0 - Solaris V8

After working with Oracle on NT for several years, I'm making my first tentative steps into the Unix world. I have 3 boxes running Solaris and Oracle 8.1.7.0. The initial install and setup was done by our Unix admin group and the application vendor, with me looking on. Now I am beginning some additional setup work.

The first thing I wanted to do was get the Oracle agent running so I could set up some OEM alerting. The OEM Mgmt Server is running on an NT box. A check of the unix box with 'lsnrctl dbsnmp_status' showed the agent wasn't yet running. Following the docs, I then did a lsnrctl dbsnmp_start. That resulted in the following msgs:

• begin quote ====
  $ lsnrctl dbsnmp_status
  

LSNRCTL for Solaris: Version 8.1.7.0.0 - Production on 18-FEB-2003 11:37:04

(c) Copyright 1998 Oracle Corporation. All rights reserved.

The db subagent is not started.
$ lsnrctl dbsnmp_start

LSNRCTL for Solaris: Version 8.1.7.0.0 - Production on 18-FEB-2003 11:37:28

(c) Copyright 1998 Oracle Corporation. All rights reserved.

$ Certain conflicts were resolved during discovery
Please consult /u01/app/oracle/product/8.1.7/network/log/nmiconf.log for details

$ lsnrctl dbsnmp_status

LSNRCTL for Solaris: Version 8.1.7.0.0 - Production on 18-FEB-2003 11:39:10

(c) Copyright 1998 Oracle Corporation. All rights reserved.

The db subagent is already running.
$
=== end quote ====

So it appears the agent started, but with some problems. The nmiconf.log file says:

• begin quote (some data masked) ====

DBSNMP for SunOS 5.8: release 8.1.7 - Production on 18-FEB-03 11:37:29 Discovering services on ncens172 configured on host addresses {ncens172 ncens172.xxx.xxx 10.xx.xx.xx ncens172p 10.xx.xx.xx} Using oratab file /var/opt/oracle/oratab Warning : LISTENER defined in
/u01/app/oracle/product/8.1.7/network/admin/listener.ora will be skipped, because it does not monitor any of the valid SIDs {MOVEX CMPM1240}
Warning : No Listener found for SID MOVEX. MOVEX will be skipped Warning : No Listener found for SID CMPM1240. CMPM1240 will be skipped === end quote ====

As a point of clarification in the above log, ORACLE_SID is *incorrctly* set to MOVEX. There is no MOVEX sid. On the other hand, CMPM1240 *is* a vaild sid and *is* listed in oratab.

At this point, it appears that the agent is running. Lsnrctl says it is, and OEM was able to discover the node. However, when OEM discovered the node, it did *not* discover the database.

So --- what am I seeing here, where do I go from here?

SELECT comments,

               insights,
               applicable_knowledge

FROM newsgroup_participants
WHERE info_usefulness = 'APPLICABLE'; Received on Wed Feb 19 2003 - 10:46:05 CST