EM 13c, EM12c: How to Modify or Increase Enterprise Manager Cloud Control Agent JVM Heap and Permgen Memory (Doc ID 1399201.1)

Last updated on SEPTEMBER 29, 2021

Applies to:

Goal

To modify or increase the JVM Heap or Permgen Size:

This is useful for cases where the agent start fails or restarts frequently or becomes unresponsive and the following messages are seen in logs

$/AGENT_INST/bin/emctl start agent

Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Starting agent .........................................Consult emctl.log and emagent.nohup in: /u03/cloud12c/agent12c/agent_inst/sysman/log

$/AGENT_INST/sysman/log/emagent.nohup reports following memory error

----- Tue Dec  9 13:19:52 2014::663::Agent Launched with PID 724 at time Tue Dec  9 13:19:52 2014 -----
2014-12-09 13:19:52,282 [1:main] WARN - Missing filename for log handler 'opsscfg'
Agent is going down due to an OutOfMemoryError
----- Tue Dec  9 13:20:24 2014::663::Checking status of EMAgent : 724 -----
----- Tue Dec  9 13:20:29 2014::663::Checking status of EMAgent : 724 -----
----- Tue Dec  9 13:20:29 2014::663::EMAgent exited at Tue Dec  9 13:20:29 2014 with return value 57. -----
----- Tue Dec  9 13:20:29 2014::663::EMAgent will be restarted because of an Out of Memory Exception. -----
----- Tue Dec  9 13:20:29 2014::663::Restarting EMAgent. -----

$/AGENT_INST/sysman/log/gcagent.log reports following memory error

2014-12-09 13:20:05,048 [33:EE0F717F:HTTP Listener-33 - Acceptor0 SslSelectChannelConnector@0.0.0.0:3872] WARN - *jetty*: EXCEPTION
java.lang.OutOfMemoryError: Java heap space
2014-12-09 13:20:05,471 [33:EE0F717F] WARN - *jetty*: EXCEPTION
java.lang.OutOfMemoryError: Java heap space

$/AGENT_INST/bin/emctl start agent

Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
Starting agent ......................................................................... failed.
Fatal agent error: Target Interaction Manager failed at Startup
Fatal agent error: Target Interaction Manager failed at Startup
Fatal agent error: Target Interaction Manager failed at Startup
EMAgent is Thrashing. Exiting watchdog

$/AGENT_INST/sysman/log/emagent.nohup reports following error 

2013-11-01 17:29:38,596 [1:main] WARN - Missing filename for log handler 'opsscfg'
Agent is going down due to an OutOfMemoryError

$/AGENT_INST/sysman/log/gcagent.log reports following error

2013-11-01 17:29:19,204 [1:3305B9] INFO - Invoking STARTUP_P1 (1) on Target Interaction Manager
2013-11-01 17:29:23,255 [1:main] FATAL - Fatal error: Target Interaction Manager failed at Startup
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)

OR

$/AGENT_INST/sysman/log/gcagent.log reports following error

Solution

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