Views:

Summary

While attempting to run Advanced Recovery jobs with a UNIX or Linux master server, the job may quickly fail, citing an SVH process went down" error in the job log. "

 

 

Symptoms

 

 

Should this occur, the JVM process will produce a core file in the DPX bin directory. The java core file will include specific information regarding the nature of the error. The file will differ depending on the operating system, architecture, and JVM version.

 

 

In addition, an SVH log file, with a filename that resembles the following, will appear in the DPX log directory:

svhstdlog.610432.txt

This log file will contain error messages similar to the ones shown below:

JVMDG217: Dump Handler is Processing a Signal - Please Wait.

JVMDG303: JVM Requesting Java core file

JVMDG304: Java core file written to /BEX-mastr/BEX/bin/javacore401466.1239039529.txt

JVMDG215: Dump Handler has Processed Exception Signal 11.

 

Resolution

 

 

The most likely cause of this issue is the JVM running out of available heap space. Thus, increasing the heap space to 1024m can resolve this issue.

 

 

In order to increase the heap space, follow the below procedure:

  1. Edit the script file sssvh found in the DPX bin directory.
  2. Locate a line of code that resembles the following:

    ./run.java.common -jar $SSPRODIR/lib/SVH.jar $SSSVH_ARGS>> $SSPRODIR/logs/svhstdlog.$$.txt 2>&1
     
  3. Add the -Xmx1024m component after the run.java.common command such that the resulting line looks like this:

    ./run.java.common -Xmx1024m -jar $SSPRODIR/lib/SVH.jar $SSSVH_ARGS>> $SSPRODIR/logs/svhstdlog.$$.txt 2>&1
     

If increasing the heap space to 1024m does not resolve this issue and the machine has enough system memory, try increasing the heap space to 2048m by adding -Xmx2048m in place of -Xmx1024m. For 64-bit platforms, increasing the heap space to 3GB or more is also possible but should only be tried if the DPX environment and catalog are extremely large.