My Oracle Support Banner

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

Last updated on FEBRUARY 19, 2020

Applies to:

Enterprise Manager Base Platform - Version 10.2.0.5 to 10.2.0.5 [Release 10.2]
Information in this document applies to any platform.
Checked for relevance on 07-Oct-2013

Goal

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 java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95)
at oracle.dms.collector.Ajp13Connector.readResponseChunk(Ajp13Connector.java:587)
at oracle.dms.collector.Ajp13Connector.readResponse(Ajp13Connector.java:542)
at oracle.dms.collector.Ajp13Connector.connectSpy(Ajp13Connector.java:245)
at oracle.dms.collector.DMSConnector.connect(DMSConnector.java:129)
at oracle.dms.collector.Hunter.queryTable(Hunter.java:285)
at oracle.dms.collector.Hunter.queryTablesByLiaisons(Hunter.java:187)
at oracle.dms.collector.Gatherer.gather(Gatherer.java:213)
at oracle.dms.collector.GatherThread.run(GatherThread.java:96)
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.

Solution

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
Goal
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.