EM 12c, 13c: Agent is going down with Out of Memory Exception though Xmx is set to a High Value (Doc ID 2667383.1)

Last updated on FEBRUARY 01, 2024

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.3.0 and later
Information in this document applies to any platform.

Symptoms

EM 12c Agent on AIX restarts frequently by generating the following errors in emagent.nohup

$AGENT_INST_HOME/sysman/log/emagent.nohup

JVMDUMP032I JVM requested Snap dump using '/u01/app/oracle/agent12c/agent_inst/sysman/emd/Snap.20200427.095724.42991784.0012.trc' in response to an event
JVMDUMP010I Snap dump written to /u01/app/oracle/agent12c/agent_inst/sysman/emd/Snap.20200427.095724.42991784.0012.trc
JVMDUMP013I Processed dump event "systhrow", detail "java/lang/OutOfMemoryError".
Agent is going down due to an OutOfMemoryError
----- Mon Apr 27 09:57:56 2020::27787482::Checking status of EMAgent : 42991784 -----
----- Mon Apr 27 09:58:07 2020::27787482::Checking status of EMAgent : 42991784 -----
----- Mon Apr 27 09:58:07 2020::27787482::EMAgent exited at Mon Apr 27 09:58:07 2020 with return value 57. -----
----- Mon Apr 27 09:58:07 2020::27787482::EMAgent will be restarted because of an Out of Memory Exception. -----

Agent is just monitoring low number of targets and Xmx value is already set to 512MB which should be sufficient to stop these OOM errors.

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

EM 12c, 13c: Agent is going down with Out of Memory Exception though Xmx is set to a High Value (Doc ID 2667383.1)

Applies to:

Symptoms

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!