My Oracle Support Banner

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

Last updated on FEBRUARY 03, 2023

Applies to:

Enterprise Manager for Oracle Database - Version and later
Information in this document applies to any platform.
Database instance status pending in Enterprise Manager 12c


The 'Metric Collection Error' status for a database target in Enterprise Manager (EM) Cloud Control means that the underlying metric which determines the database 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 database is reflected.  This article is useful to troubleshoot issues such as:

Database instance 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
Troubleshooting Steps
 A) How to find out the full metric collection error?
 1) View the Underlying Error Message in the Console
 2) View the Full Errors in EMDIAG kit Reports
 B) Steps to Troubleshoot the metric collection error
 1) Find out the full message associated with the metric collection error
 2) Analyze the target availability dump
 3) Check agent errors.
 4) Check whether the agent can currently evaluate the metric
 5) Check if the metric is scheduled to run
 6) Force the metric to run
 7) Check for suspended metrics
 8) Reload the dynamic properties
 9) Check for existence of database plugin
 10) Simulate the query that the agent runs to calculate 'Response'
 11) Collect Log Files
  C) Common Metric Collection Errors
 i) Error message :oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Error while streaming Broken pipe.
 ii) Compute dynamic property takes too long
 iii) No such metadata for target type [oracle_database] for target [oracle_database.<databaseName>]
 iv) Error Message: oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Timeout during collection:oracle.sysman.gcagent.task.TaskTimeOut: 60000 MILLISECONDS for oracle_database:<databaseName>:Response
 v) Error Message:Missing Properties
 Case Studies
 D) Case Study 1:Database Plugin is Not deployed
 1) View the Metric Collection Error in the Console
 2) View the information from EMDIAG target tump
 3) View output from emctl config agent listtargets
 4) View output from emctl listplugins agent
 E) Case Study 2:"Dynamic property takes too long"
 1) view the metric collection error message
 2) View EMDIAG kit information
 3) View Metric Browser
 4) Check from the agent home
 5) Force the metric to Run
 6) Fix the issue

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