EM 13c, EM 12c: How to Troubleshoot the Listener Status (Up, Down) in Enterprise Manager Cloud Control (Doc ID 1534401.1)

Last updated on DECEMBER 11, 2023

Applies to:

Enterprise Manager for Oracle Database - Version 12.1.0.4.0 and later
Oracle Net Services - Version 11.2.0.3 to 11.2.0.3 [Release 11.2]
Information in this document applies to any platform.
Listener status Down in Enterprise Manager 12c
Listener status Down in Enterprise Manager 13c

Purpose

To understand how the listener availability status is calculated in Enterprise Manager (EM) 12c Cloud Control. To provide steps to troubleshoot if the listener is showing incorrect status.

Troubleshooting Steps

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Troubleshooting Steps

About the Listener Availability Metric

A) Where is the Listener Monitoring Configuration Info stored?

B) Troubleshooting the Listener Up/down Status

1) Check to see if there is an error message associated with the down status.

2) check whether the listener name, listener directory and machine name 'monitoring configuration details' stored in Cloud Control are correct.

3) Confirm that the ORACLE_HOME of the listener defined in the monitoring configuration is correct

4a) Use the entries from targets.xml to double check the listener information

4b) Simulate the EM tnsping command

5) Is the machine name defined correctly?

6) Check whether the response metric is running

7) Check whether the agent can currently evaluate the metric correctly

8) Check the severity history of the target on the agent itself.

9) Manually run the metric collection.

10) Perform a clearstate on the agent

11) Run the lsnrresp.pl script manually

C) Commonly hit scenarios which cause incorrect listener status

i) The listener is down: tnsping not found in/bin.

ii) A listener process behavior and identity is defined by not just the listening end-points (the 'Host' and 'Port'), but also by the "Listener Parameter File" (listener.ora) which was used to start the listener process. The "Listener Parameter File" defines parameters like, logging and tracing levels, log/trace directories etc. in addition to the listening end-points, and hence, its location is essential for EM to uniquely identify a "Listener Target".

iii) Listener is configured for TCPS.

iv)Listener using IPC protocol shows as down.

v) 9i Listener using a password shows as down. (TNS-01169: The listener has not recognized the password)

vi) Symptom: Listener is down. Accompanying message is "Failed to run lsnrctl"

Information to Collect

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.