Grid Control Agent Consumes High Memory while Monitoring Netapp Targets
(Doc ID 735947.1)
Last updated on NOVEMBER 09, 2019
Enterprise Manager Base Platform - Version 10.2.0.4 to 10.2.0.4 [Release 10.2] Information in this document applies to any platform.
While monitoring netapp targets the memory used by agent increases rapidly.
The error stack in emagent.trc is generic as below:
(pid=296): emagent started successfully URLTiming: Using SunX509 ERROR in REQUEST RESPONSE code = 400. text = --- Recycling process. VMSize is 423.75843098 MB increased by 3.28374653 MB in past 1 --- ----- <timestamp>::Received restart request from EMAgent : 296 ----- ----- <timestamp>::Stopping EMAgent : 296 ----- (pid=296): emagent now exiting normally ----- <timestamp>::Agent Launched with PID 756 at time <timestamp> ----- (pid=756): starting emagent version 10.2.0.4.0 (pid=756): emagent started successfully
This issue has started to occur after upgrading the agent to 10.2.0.4.0 on AIX platform, but the patch is available on multiple platforms.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!