Common problems running the Intelligent Agent on UNIX


Subject:            Common problems running the Intelligent Agent on UNIX
Creator:            SDADDOLA
Modified:           21 Apr 97 05:12:20           



	Common problems when running the Intelligent Agent on UNIX
	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

(1) Introduction.
(2) Handling Agent warning: NMS-00001.
(3) Handling Agent error: NMS-00205.
(4) Handling Agent error: NMS-00007.
(5) Handling Agent error: NNL-00018.
(6) Agent memory leak.

(1) Introduction:
~~~~~~~~~~~~~~~~~

This note attempts to document some of the problems and their solutions which 
have been experienced when configuring and running Oracle Enterprise Manager 
Intelligent Agent on UNIX platforms. The issues documented in this note affect
the Intelligent Agent released with server release 7.3.2/OEM 1.2.2. The 
solutions
may not be relevant for later versions of Intelligent Agent.

Ensure the Intelligent Agent patch is applied to releases prior to 7.3.3.
information.

(2) Intelligent Agent issues warning NMS-00001:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

When starting the Intelligent Agent the following message is issued;

LSNRCTL> dbsnmp_start
NMS-00001: Warning: dbsnmp unable to connect to SNMP master agent

Solution:
~~~~~~~~~

This is just a warning message which can be safely ignored. It occurs because
the Agent tries to contact the SNMP daemon on the local server. SNMP does not
have to be configured or running to use OEM. To suppress this message, add the
following lines to the SNMP.ORA file on the local server;

NMI.LOG_DIRECTORY=<ORACLE_HOME>/network/log
NMI.LOG_FILE=snmp

The warning message will now be written to the file snmp.log in the appropriate
directory.

(3) Intelligent Agent fails to start:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Attempting to start the Intelligent Agent fails in the following way;

LSNRCTL> dbsnmp_start
NMS-00001: Warning: dbsnmp unable to connect to SNMP master agent
NMS-00205: Failure to connect to database <alias> with 
	username/password dbsnmp/dbsnmp@<alias>

Solution:
~~~~~~~~~

This is most likely caused by the failure to precreate the DBSNMP synonym. 
To do this, set you current directory to the $ORACLE_HOME/network/admin 
directory of the installed server v7.3 on the UNIX server. This is the 
ORACLE_HOME from which the Intelligent Agent must be started.

Connect to the database idenitfied by the <alias> string from the NMS-00205
error message and the SYS users and run the catsnmp.sql script;

	ORACLE_HOME=/oracle2/OFA_base/app/oracle/product/7.3.2.3

	cd $ORACLE_HOME/network/admin
	svrmgrl sys/manager@<alias>
	SVRMGR> @catsnmp

Repeat this operation against each database which is to be monitored by Oracle 
Enterpise Manager. The Intelligent Agent should start successfully once each 
monitored database has been updated.

(4) NMS-00007 error on Agent startup:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

An attempt to start the Intelligent Agent fails with;

	NMS-00007: dbsnmp failed to allocate memory 

Solution:
~~~~~~~~~

This is rare if the configuration files have been generated with Network Manager
and is usually caused by a configuration error in the SNMP.ORA file. Check this
file for syntax errors.

(5) NNL-00018 error on Agent startup:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

An attempt to start the Intelligent Agent fails with;

NNL-00018: warning: could not contact default name server
Total response time:   0.30 seconds
Response status:       NNC-00409: temporary name service failure
NL-00851: control program finished

Solution:
~~~~~~~~~

This is a common error. Be default the Agent will attempt to register with a
local Oracle Names service. If Names is not running then this error will occur.
The solution is to add the following line to the SNMP.ORA file on the server;

NMI.REGISTER_WITH_NAMES=FALSE

(6) Intelligent Agent memory leak:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

When starting the Oracle Enterprise Manager Intelligent Agent on UNIX it is 
possible to see an apparently idle Agent suffer from a severe memory leak.

The scenario under which this occurs varies between platforms where is has been
observed. The severity of the memory leak likewise varies between platforms and 
even operating system releases.

One common cause of this problem is a configuration error in the SNMP.ORA file
on the server which the Agent uses to identify the databases to monitor.

If the SNMP.ORA file contains references to a sqlnet alias which do not exist
in the local TNSNAMES.ORA or in ORACLE NAMES, then the memeory leak can manifest
itself.

Other scenarios include the SNMP.ORA file containing references to databases or
listeners which have not been started when the Agent is started and are thus 
inaccessible to the Agent.

Solution:
~~~~~~~~~

Make sure that every entry in the SNMP.ORA file has a matching entry in the
TNSNAMES.ORA file or an entry in the NAMES server. For example;

The SNMP.ORA file will contain an entry similar to the following;

SNMP.VISIBLESERVICES =(LISTENER_isis.uk.oracle.com,isis_V7323.uk.oracle.com)
SNMP.INDEX.LISTENER_isis.uk.oracle.com = 10
SNMP.INDEX.isis_V7323.uk.oracle.com = 13
SNMP.SID.isis_V7323.uk.oracle.com = V7323
SNMP.ORACLEHOME.isis_V7323.uk.oracle.com = ...

Make sure that the referenced sqlnet alias, "isis_V7323.uk.oracle.com" in this
example, is defined in the TNSNAMES.ORA file.