My Oracle Support Banner

EM 13.4 : Agent Unable to Start With Error "Max heap size too large for Compressed Oops" (Doc ID 2821177.1)

Last updated on NOVEMBER 15, 2021

Applies to:

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

Symptoms

EM 13c Agent failed to start.
Observed below errors in <AGENT_INST>/sysman/log/emagent.nohup:

----- 2021-11-12 15:04:49,791::17699::Launching the JVM with following options: -Xmx3171316736M -XX:MaxMetaspaceSize=224M -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:-UseLargePages -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -DHTTPClient.dontSeekTerminatingChunk=true -----
----- 2021-11-12 15:04:49,792::17699::Agent Launched with PID 17749 at time 2021-11-12 15:04:49,792 -----
----- 2021-11-12 15:04:49,792::17749::Time elapsed between Launch of Watchdog process and execing EMAgent is 1 secs -----
----- 2021-11-12 15:04:49,792::17699::Previous Thrash State(-1,-1) -----
Java HotSpot(TM) 64-Bit Server VM warning: Max heap size too large for Compressed Oops
Error occurred during initialization of VM
Could not reserve enough space for 3247428337664KB object heap



Changes

 

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
Symptoms
Changes
Cause
Solution
References


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