My Oracle Support Banner

Enterprise Manager 12c/13c Cloud Control Agent Diagnostic Incidents Known Issues (Doc ID 2592958.1)

Last updated on AUGUST 19, 2022

Applies to:

Enterprise Manager Base Platform - Version and later
Information in this document applies to any platform.


This document contains a list of known issues for 12c/13c Management Agent specific diagnostic incidents.

An incident is a single occurrence of a problem (critical error) that occurred in the Management Agent process while using Enterprise Manager. Diagnostic incidents usually indicate software errors and should be reported to Oracle using the Enterprise Manager Support Workbench.

A diagnostic incident logged for the Management agent will be recognized as:

1. The AGENT_INST_HOME/sysman/log/emagent.nohup file will show entries like:

Nov 03, 2016 11:08:14 AM oracle.sysman.diag.EMDiagImpl createIncident.648
INFO: incident 565 created with problem key java.lang.NullPointerException:oracle.sysman.gcagent.state.StateMgr:1096, in directory AGENT_INST_HOME/diag/ofm/emagent/emagent/incident/incdir_565
Nov 03, 2016 11:38:13 AM oracle.sysman.diag.EMDiagImpl captureDiagData.478
SEVERE: Critical error: <no message>


2. A notification or alert will be raised on the Management Agent target similar to:

Target type=Agent
Target name=host.<DOMAIN_NAME>:3872
Incident creation time=Jan 31, 2016 7:23:21 AM EST
Last updated time=Jan 31, 2016 7:23:43 AM EST
Message=Internal error detected: java.lang.Throwable:oracle.sysman.gcagent.task.scheduler.DispatchingTaskScheduler:1071.
Metric Group=Incident
Metric=Diagnostic Incident
Metric value=diagnosticIncident


 EM 12c, EM 13c Cloud Control Management Agents


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 summary
 Known issues 

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