Grid Control 10g and 11g - How to Increase the Virtual Memory Limit for the Agent to Avoid Unnecessary Agent Re-starts? (Doc ID 428410.1)

Last updated on AUGUST 19, 2015

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.3 to 11.1.0.1 [Release 10.2 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 26-08-2012***

Goal

The Agent watchdog can cause a Recycle of the Agent if it detects an abnormal increase in memory usage, the Agent watchdog has logic to prevent the agent processes from leaking memory and using up too much system resources. However, newer OS and newer builds of code tend to use larger amounts of memory as a baseline.

This might also happen when there are many targets being monitored, the default values might not be sufficient, leading the watchdog to assume that the Agent is consuming too many resources and hence recycles it.

There are no abnormal terminations or hangs detected so no core dump files get generated.

Content of the <AGENT_HOME>/sysman/log/emagent.nohup has the following entries:

--- Recycling process. VMSize is 215.9140625 MB increased by 107.1953125 MB
in past 1 ---
----- Sat Apr 26 20:16:41 2008::Received restart request from EMAgent : 18662
-----
----- Sat Apr 26 20:16:41 2008::Stopping EMAgent : 18662 -----
(pid=18662): emagent now exiting normally
----- Sat Apr 26 20:16:52 2008::Agent Launched with PID 5284 at time Sat Apr
26 20:16:52 2008 -----
(pid=5284): starting emagent version 10.2.0.3.0
(pid=5284): emagent started successfully

Solution

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