Details about 'Agent Misconfiguration' Alerts in Grid Console 10.2 and How to Resolve them
(Doc ID 741595.1)
Last updated on JULY 12, 2021
Applies to:Enterprise Manager Base Platform - Version 10.2.0.5 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
Checked for relevance on 08-Sep-2010
Checked for relevance on 07-Nov-2013
The purpose of this document is to provide some recommendations for resolving Misconfigured Agent Alerts. A Misconfigured Agent is an Agent that is not able to perform a heartbeat or upload information to the Oracle Management Service (OMS) due to invalid configuration or invalid data.
This is a new feature added in Grid Control 10.2.0.5 and the list of Misconfigured Agents can be found in these pages:
- Alerts -> Critical Page
- Setup -> Agents -> "Misconfiguration Alerts and Blocked Agents" Page.
Agent misconfiguration alerts are triggered by the following Metrics of the Agent target:
- Consecutive metadata upload failure count
- Consecutive heartbeat failure count
- Consecutive severity upload failure count
- OMS Agent time skew
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