Java problems impact data collection

As a rule of thumb, BMC PATROL for SAP Solution Manager requires about 0.5 megabytes of Java process memory for each monitored CCMS parameter. Insufficient Java process memory causes the JVM to crash, producing a dump on the operating system. As a result, BMC PATROL for SAP Solution Manager cannot collect data and cannot monitor the SAP environment.

To troubleshoot this issue, you must define a larger Java memory heap size.

To define a larger memory heap size

1. Through the pconfig utility, locate the /SSM/SYSTEMS/ javaExecuteArguments variable (described on page 56).

2. Within the value of the javaExecuteArguments variable, include definitions for a larger Java memory size, as in the following example:
   -Xms256m -Xmx768m

   Note

   For an AIX operating system, include an additional argument for enabling verbose garbage collection, as in the following example: -verbosegc -Xms256m -Xmx768m

3. Restart the PATROL Agent.
4. Restart the Java Data Collector, as described in Stopping and starting the Java Data Collector.