EM的報錯解決：oracle.sysman.gcagent.target.……ConfigStateMgr:798

to_be_Dba發表於2015-10-29
OracleGC

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/，如需轉載，請註明出處，否則將追究法律責任。

相關文章