EM的报错解决：oracle.sysman.gcagent.target.……ConfigStateMgr:798

EM中今天报了一个错误：

EM Event: Critical:db0120:3872 - Internal error detected: java.lang.IllegalStateException:oracle.sysman.gcagent.target.interaction.execution.ConfigStateMgr:798

参照 官方文档1458858.1，检查并比较该服务器agent目录 ，发现最新的storage_*.xml是13年的，而其他正常服务器上的该文件都是最近两天的。原因大概是以前收集的信息中 存在非法的控制字符，导致无法上传，因此一直无法生成新的文件。

该服务器的症状与该文档描述完全一致，因此将storage_*.xml移走，并重启了agent。后面未再发生此告警。

下面是MOS文档：

APPLIES TO:

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

SYMPTOMS

Agent 12c raises periodically the following alerts :

Severity=CriticalAlert EM Event: <hostname>:<port> - Internal error detected: java.lang.IllegalStateException:oracle.sysman.gcagent.target.interaction.execution.ConfigStateMgr:798.

Target type=Agent
Target name=<hostname:port>
Categories=Diagnostics
Message=Internal error detected: java.lang.IllegalStateException:oracle.sysman.gcagent.target.interaction.execution.ConfigStateMgr:798.

The below exceptions are seen in <Cloud12c_Middleware_Home>/agent/agent_inst/sysman/log/gcagent_errors.log

2012-04-23 20:27:49,130 [222:GC.Executor.7 (host:devdb02.oogway.bskyb.com:host_storage) (host:devdb02.oogway.bskyb.com:host_storage:storage_reporting_data)] ERROR - null
javax.xml.bind.UnmarshalException
- with linked exception:
[org.xml.sax.SAXParseException: <Line 1, Column 5750>: XML-20221: (Fatal Error) Invalid char in text.]
at javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(AbstractUnmarshallerImpl.java:315)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalException(UnmarshallerImpl.java:514)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:215)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:190)
at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:241)
at oracle.sysman.gcagent.mbl.DataCollectionMbl.unserialize(DataCollectionMbl.java:599)

CAUSE

 Bug:13547855 12C METRIC COLLECTION ERROR FOR ALL STORAGE METRICS

There were old storage xml files which could not be uploaded because the data collected includedstrings with invalid control characters.

New collections are not started as long as old data are available: as the files could not be uploaded, they were never removed.

SOLUTION

Remove <agent_inst>/sysman/emd/state/configstate/host/<nodename>/storage_*.xml files.

Restart the agent.

This will restart the collection of the storage data. As these data are collected evry 24 hours, please wait for at least 24 hours to check the report.

You can also run the collection manually:

$ emctl control agent runCollection <hostname>:host host_storage

 

Example:

$ emctl control agent runCollection myhost.mydomain:host host_storage

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/26451536/viewspace-1818665/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/26451536/viewspace-1818665/