EM 12c: After Successful Auto Tuning, Agent Crashes With Error 'Agent is going down due to an OutOfMemoryError'

(Doc ID 1608080.1)

Last updated on OCTOBER 29, 2016

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 to 12.1.0.3.0 [Release 12.1]
Information in this document applies to any platform.

Symptoms

The 12.1.0.1/2 agent stops frequently

/AGENT_INST//sysman/log/emagent.nohup reports the following exception

----- Sun Nov 17 10:33:15 2013::1021::Checking status of EMAgent : 1176 -----
Agent is going down due to an OutOfMemoryError
----- Sun Nov 17 10:33:46 2013::1021::Checking status of EMAgent : 1176 -----
----- Sun Nov 17 10:33:46 2013::1021::EMAgent exited at Sun Nov 17 10:33:46 2013 with return value 55. -----
----- Sun Nov 17 10:33:46 2013::1021::EMAgent has exited due to initialization failure. -----
----- Sun Nov 17 10:33:46 2013::1021::Stopping other components. -----
----- Sun Nov 17 10:33:46 2013::1021::Commiting Process death. -----

The agent restarted and the log file shows that Auto Tuning ran successfully at one of the agent restarts

UploadMaxBytesXML=50.0
_SchedulePersistTimer=30
MaxThreads=10
agentJavaDefines=-Xmx128M -XX:MaxPermSize=96M
SchedulerRandomSpreadMins=60
UploadMaxNumberXML=5000
Auto tuning was successful

However after this successful Auto Tuning, the agent ran out of memory again

Cause

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