My Oracle Support Banner

Grid Agent Configuration: How to Increase the Java Memory for the Grid Agent? (Doc ID 952914.1)

Last updated on AUGUST 19, 2022

Applies to:

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


When the Grid Agent is performing a resource-intensive operation, entries as below could be shown in the <AGENT_HOME>/sysman/log/emagent.nohup file:

(pid=19223): emagent started successfully
URLTiming: Using SunX509
Exception in thread "oracle.dms.collector.GatherThread@15000" java.lang.OutOfMemoryError: Java
heap space
at oracle.dms.collector.Ajp13Connector.readResponseChunk(
at oracle.dms.collector.Ajp13Connector.readResponse(
at oracle.dms.collector.Ajp13Connector.connectSpy(
at oracle.dms.collector.DMSConnector.connect(
at oracle.dms.collector.Hunter.queryTable(
at oracle.dms.collector.Hunter.queryTablesByLiaisons(
at oracle.dms.collector.Gatherer.gather(
Exception in thread "oracle.dms.collector.Hunter" java.lang.OutOfMemoryError: Java heap space

This document explains how the Java heap size value can be increased for the Grid Agent to avoid the above errors.


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.