Issue 1: In Saas Helix Environment the job fails due to Java heap size error

Issue 2 : In On Prem environment the job fails due to Java heap size error

In case a job in Atrium Integrator Console shows JAVA heap space error during execution.

(java.lang.OutOfMemoryError: Java heap space) and increasing java heap size to 2G still the error occurs.

PENTAHO_DI_JAVA_OPTIONS="-Xmx2g -XX:MaxPermSize=256m"

Issue 3:  java.lang.OutOfMemoryError: Java heap space in custom job

For Versions above 1805, perform the below steps to increase the memory for the carte process:

Scenario 1: The job shows In progress and no actions taken and arcarte log shows java.lang.OutOfMemoryError: Java heap space)

Please raise a CRQ as so that customer can approve the CRQ
Steps:
1) Take necessary approval that is done before cops deployment
2) Take necessary backup that is taken before cops deployment
3) Search for the project name and open the remedy project of that customer
> Configuration tab and change below parameters:
Platform FTS DI Server (Carte) Size - (Set this to max based on value present also discuss with R & D on this)
4) Save the changes
5) Go to deployment tab and deploy using "HELIX_DEPLOY_PLATFORM" button
6) Observe the deployment is completing successfully
7) Verify all pods are up
 

Scenario 2: In Saas Helix customer the job was failing due to Java heap size error 

1. Disable row level logging on DMT run

2. Disable row level logging on CMDB run as well

3. Once the log level is disabled the job worked fine from DMT and CMDB console without Java heap error.

Scenario 3 : In On Prem environment the job was failing due to Java heap size error ( java.lang.OutOfMemoryError: Java heap space)

Follow below the steps to increase the cache for the AI plugin.

1. Open the arminitor.cfg/armonitor.conf file.

(Windows) ARSystemServerInstallDir\Conf\armonitor.cfg

(UNIX) /etc/arsystem/serverName/armonitor.conf

2. Set the -Xmx2048m or more according to your requirement(There is no upper limit however this paremeter is limited to the available memory on the environmen)

"%BMC_JAVA_HOME%\java.exe" -Xmx2048m -classpath "C:\Program Files\Java\jre1.8.0_181\lib\ext\*;C:\Program Files\Java\jre1.8.0_181\lib\*;C:\Program Files\BMC Software\ARSystem\diserver\data-integration\*;C:\Program Files\BMC Software\ARSystem\diserver\data-integration\lib\*" "-Dorg.mortbay.util.URI.charset=UTF-8" "-DKETTLE_HOME=C:\Program Files\BMC Software\ARSystem\diserver" "-DKETTLE_REPOSITORY=" "-DKETTLE_USER=" "-DKETTLE_PASSWORD=" "-DKETTLE_PLUGIN_PACKAGES=" "-DKETTLE_LOG_SIZE_LIMIT=" "-DKETTLE_MAX_LOG_SIZE_IN_LINES=5000" "-DKETTLE_DISABLE_CONSOLE_LOGGING=Y" "-DKETTLE_COMPATIBILITY_MERGE_ROWS_USE_REFERENCE_STREAM_WHEN_IDENTICAL=Y" "-DKETTLE_LENIENT_STRING_TO_NUMBER_CONVERSION=Y" org.pentaho.di.www.Carte <ServerName>.bmc.com 20000 -i "C:\Program Files\BMC Software\ARSystem"
3. Save the file. 
4. Reload the plugin by killing the java process for the "diserver" or restart the AR Server process.
Dividing the information processed by a job presenting the issue is advised.

Also, VIDEO for on prem fix can be checked.
https://www.youtube.com/watch?v=97X6ymeI5s4&ab_channel=BMCHelixRemedyandDiscovery

4. In the lookup step or the mapping step the fields referred should be actually present