EM 13c: Numerous Incidents: java.lang.NullPointerException:oracle.sysman.gcagent.state.StateMgr:1096 are Generated for the Agents Monitoring HAS targets

(Doc ID 2226172.1)

Last updated on MAY 10, 2018

Applies to:

Enterprise Manager for Oracle Database - Version 13.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

Numerous incidents are generated for the EM 13.2 Agents, monitoring HAS targets, with this error message:

java.lang.NullPointerException:oracle.sysman.gcagent.state.StateMgr:1096

From <agent base directory>/agent_inst/sysman/log/emagent.nohup file

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>
java.lang.NullPointerException


The incident <Agent_Inst_Home>/diag/ofm/emagent/emagent/incident/incdir_<ID>/readme.txt file has this typical error stack:

Incident Id: 1
Incident Source: SYSTEM
Create Time: <timestamp>
Problem Key: java.lang.NullPointerException:oracle.sysman.gcagent.state.StateMgr:1096
ECID: b3b689a8-8c4c-ac97-1ce116a3.0
Thread Id: 28
Error Message Id: OFM-99999

Context Values
--------------
TARGET_ID : has.<has target name>
threadName : GC.Executor.2503 (has:<has target name>:CRSAlert11gR2_dup)
METRIC_NAME : clusterware_alerts

Stack Trace
-----------
java.lang.NullPointerException
at oracle.sysman.gcagent.state.StateMgr.upsertStateEntry(StateMgr.java:1096)
at oracle.sysman.gcagent.state.StateMgr.upsertStateEntry(StateMgr.java:1063)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.updateLastEvalTS(ExecuteTask.java:2770)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.processMultipleResultSetForTimestamp(ExecuteTask.java:3742)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.processMultipleResultSet(ExecuteTask.java:3669)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.runTask(ExecuteTask.java:3287)
at oracle.sysman.gcagent.target.interaction.execution.ExecuteTask.call(ExecuteTask.java:4249)
at oracle.sysman.gcagent.metadata.impl.collection.MetricColl$1.call(MetricColl.java:552)
.............

From <agent base directory>/agent_inst/sysman/log/gcagent.log:

2016-11-03 11:08:13,775 [26283:GC.Executor.163 (has:<has target name>:CRSAlert11gR2_dup)] DEBUG - Executing cleanup action End session [145782] for task has:has_<has target name>:CRSAlert11gR2_dup
2016-11-03 11:08:13,775 [28:IncCreHandler] DEBUG - Adding diag fact [INVOKER_STACK] to thread 28: java.lang.Exception: Critical error
at oracle.sysman.gcagent.tmmain.diag.DiagManager.handleException(DiagManager.java:1019)
at oracle.sysman.gcagent.tmmain.diag.DiagManager.handleException(DiagManager.java:935)
at oracle.sysman.gcagent.tmmain.diag.DiagManager.handleException(DiagManager.java:707)
at oracle.sysman.gcagent.task.TaskFutureImpl$WrappedTask.call(TaskFutureImpl.java:736)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)

 The incidents are mainly generated when the "Oracle High Availability Service Alert Log Error" metric is executed for the HAS target.

Changes

Upgraded to 13.2 Cloud Control.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms