Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: IA subagent stopping
In 9.2.x the proper command for checking the status of the agent is:
agentctl status. In 9.2.0.4 when I enter lsnrctl dbsnmp_status is get the
followiing error:
LSNRCTL for IBM/AIX RISC System/6000: Version 9.2.0.4.0 - Production on
10-JUN-2004 09:01:05
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
NL-00853: undefined command "dbsnmp_status". Try "help"
When you start the agent you actually start 2 processes, dbsnmp and dbsnmpwd. The second was added to periodically check to see if the agent is running and start it if it is not. If you can look at the processes on the server (ps -fe |grep dbsnmp) you should see both processes. If not, stop and restart the agent.
HTH,
Ruth
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Rusnak, George A.
(SEC-Lee) CTR
Sent: Wednesday, June 09, 2004 5:13 PM
To: oracle-l_at_freelists.org
Subject: IA subagent stopping
Group,
We have set up an event from OEM (9.2.0.1) to do node checking , HP-UX
B.11.11 U 9000/800. We have within the past couple of weeks been getting
the following message for each instance on the node:
Node Name : manxx01-iiu.deca.mil
Name : Verify_ALL_DBs_Up
Target Name : CDRGE.deca.mil
Target Type : Database
Status : NODE UNREACHABLE
Node UpDown
VNI-4009 : Cannot contact agent on the node. Agent may be down or network
communication to the node has failed.
NODE UNREACHABLE
Jun 09 2004 02:06:16 PM
Database UpDown
Event test "Database UpDown" is cleared
CLEARED
Jun 08 2004 06:20:50 PM
When checking on this instance via LSNRCTL dbsnmp_status, the message is that the subagent has not been started.
Cannot say that there has not been changes made to the system. We are just running out of ides of how to run this problem to ground.
TIA
Al Rusnak
DBA - CISIS, Computer Operations