My Oracle Support Banner

EM 12c, EM 13c: Troubleshooting the Metric Collection Error status for a Listener Target in Enterprise Manager 12c and 13c Cloud Control (Doc ID 1533938.1)

Last updated on MARCH 29, 2018

Applies to:

Enterprise Manager for Oracle Database - Version 12.1.0.1.0 and later
Information in this document applies to any platform.
Listener status metric error in Enterprise Manager 12C

Purpose

The Metric Collection Error status for a listener target in Enterprise Manager (EM) Cloud Control means that the underlying metric which determines the listener availability status cannot be evaluated correctly.  The aim of this document is to try and clear the 'Metric Collection Error' status so that the true status of the listener is reflected.

This should be used to resolve problems such as:

Listener status metric error in Enterprise Manager

 

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
Purpose
Troubleshooting Steps
 What is a Listener metric collection error?
 A) How to find out the full metric collection error?
 Method 1 (view the console)
 
 Method 2 (use the EMDIAG kit)
 
 Other Relevant dumps from EMDIAG kit
 


B) What to Collect for a Listener Metric Collection Error
 1) The full metric collection error
 
2) Determine whether the Response metric is scheduled
 
3) Check whether the Response metric can be evaluated successfully
 
4) Confirm whether the agent can actively run the Response metric
 
5) Check for suspended metrics
 

6) Check whether the agent knows of the listener target 
 
7) Check whether the database plugin is deployed on the agent
 
8) Check whether the database plugin files physically exist.
 
9) Recompute the dynamic properties of the listener
 

10) Collect the log files
 


Common Listener Metric Collection Errors
 1) Metric evaluation error start - oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Attempt to reload Oraperl.pm aborted. Compilation failed in require at /oracle/app/oracle/agent/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0/scripts/dbUtil.pl line 23. BEGIN failed--compilation aborted at /oracle/app/oracle/agent/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0/scripts/dbUtil.pl line 23. Compilation failed in require at /oracle/app/oracle/agent/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0/scripts/db/esaDbUtils.pl line 31. Compilation failed in require at /oracle/app/oracle/agent/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0/scripts/db/net/listenerUtil.pl line 60. Compilation failed in require at /oracle/app/oracle/agent/core/12.1.0.1.0/../../plugins/oracle.sysman.db.agent.plugin_12.1.0.2.0/scripts/lsnrresp.pl line 53.
 2) Error occurred while deploying AGENT plug-in: java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Error while streaming JobReader:java.io.IOException: Broken pipe 
 3) Metric Collection Error - Can't resolve a non-optional query descriptor property [scriptsDir]
 4) TIMEOUT reached in computing dynamic properties for target LISTENER,oracle_listener
 


5) Target {oracle_listener.LISTENER_myhost} is broken: Missing Properties - <propertyName>
References

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