Problem - Grid Control Agent Restarts with Core Dump when it Reaches its Maximum Thread Model Limit
(Doc ID 357448.1)
Last updated on NOVEMBER 09, 2019
Applies to:
Enterprise Manager Base Platform - Version 10.1.0.2 to 10.2.0.5 [Release 10.1 to 10.2]Information in this document applies to any platform.
Checked for relevance on 31-Jan-2014
Symptoms
Running Grid 10.1.0.4 Agent, receiving email notification stating that the agent went down and then a few seconds later stating that the agent has come back up. This can occur very frequently, every 20 minutes, or every few hours, depending on the load on the node. If you check the status of the agent, it appears to be running fine, uploads are occurring. The ORACLE_HOME/sysman/log/ files show the agent core dumping, but no core file is produced:
ERRORS with agent in WARN (default) level of debugging:
emagent.nohup:
Changes
If the Agent was working fine previously and all of a sudden this has started to occur, then it may be getting caused by an increased load on the machine, for example:
- New third party software installed,
- New ORACLE software installed, new databases added or changes in the configuration.
- New targets added that will be monitored by this agent, such as new OC4J applications.
- Change in OS level tuning, either restricting thread count or a new OS patch.
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |