Available Memory

Diagnose and troubleshoot memory shortages.

If you are running out of memory, you see this error message:
java.lang.OutOfMemoryError

When you are running out of memory, either the Replication Agent drops out of Replicating state or the entire Replication Agent server stops executing.

To support adjusting the amount of memory available to the JRE, all of the executable scripts (or batch files) in the Replication Agent bin directory refer to an environment variable named RA_JAVA_MAX_MEM. All Replication Agent instance RUN scripts also reference the RA_JAVA_MAX_MEM environment variable.

On HP-UX, if the RASD runs out of memory, increase the size of maxdsiz_64bit from 2 GB (default) to 4 GB. For more information, see HP documentation.

Related concepts
Replication Agent Instance Availability Monitoring
Primary Database Log Access
Replication Agent System Logs
Skipped DDL Commands
JVM Thread Dump
Related tasks
Verifying that a Primary Database Object Is Marked for Replication
Checking the Current Replication Agent Status
Using ra_statistics to Check Replication Agent Operations and Performance
Debugging LTL
Using Trace Filters
Troubleshooting DDL Replication Failure in Replication Agent for UDB