Troubleshooting
Problem
Tivoli Storage Manager Backup/Archive (B/A) client Java GUI hang when it needs to populate a big amount of data during the restore.
Symptom
The Tivoli Storage Manager B/A client Java GUI on Microsoft Windows may hang during the enumeration of the content for certain folders that contain millions of files during a restore operation.
In this case the enumeration is still going on but no file list is visible in the GUI. The GUI may hang indefinitely and freeze in the case that there is not enough memory passed from the Java process that starts the GUI itself.
By default the GUI is started by Java process with a memory heap size of 128 MB. In the case that the heap size is exhausted the following error can be read in the application log of the Windows system:
Information <date> IBM Java 0 None "The description for Event ID " "0" " from the source " "IBM Java" was not found . Either the component that raises this event is not installed on the local computer or the installation is corrupted. , you can install or repair the component on the local computer.
If the event originated on another computer , the display information had to be saved with the event .
The following information was included with the event :
JVMDUMP032I JVM called in response to an event a dump of system with "C:\Program Files\Tivoli\TSM\baclient\core.<timestamp>.dmp"
Information <date> IBM Java 0 None "The description for Event ID" "0" " from the source " " IBM Java" was not found . Either the component that raises this event is not installed on the local computer or the installation is corrupted. , you can install or repair the component on the local computer.
The following information was included with the event :
JVMDUMP039I dump event "systhrow " ,"detail " ,"java/lang/OutOfMemoryError" to <date> - please wait.
.
Moreover in the default installation path it is possible to locate java core and heapdump.phd files.
This is a confirmation that the operation of enumerating the files consumed all the heap size memory and lead to the crash.
Environment
All windows platform
Resolving The Problem
It is possible to start the Tivoli Storage Manager GUI with a different heap size memory rather than the 128 MB default.
For starting the GUI with a different heap size follow these instructions:
1. Open a Command Prompt with administrative right (run as Administrator....)
2. Verify that the following environment variables are set on the system:
DSM_DIR =C:\Program Files\Tivoli\TSM\baclient
DSM_LOG =C:\Program Files\Tivoli\TSM\baclient
DSM_CONFIG =C:\Program Files\Tivoli\TSM\baclient\dsm.opt
3. Start the GUI with a new heapsize:
a. If on the system is installed a Oracle Java version (run java -version in a Command prompt) move to the
installation folder of the TivolI Storage Manager (default c:\program files\tivoli\tsm\baclient) and
run:
- javaw -Xmx256m -DDSM_CONFIG="%DSM_CONFIG%" -DDSM_DIR="%DSM_DIR%" -DDSM_LOG="%DSM_LOG%" -jar "dsm.jar"
b. If on the system is not installed any java version (java -version command returns an error) it is possible to use the java package delivered with the Tivoli Storage Manager Client:
Move to the following location (xxxxx is the version of the java delivered with Tivoli Storage Manager and can vary with the client version installed):
c:\program files\tivoli\tsm\baclient\\jvmxxxxx\jre\bin\
and run
javaw -Xmx256m -DDSM_CONFIG="%DSM_CONFIG%" -DDSM_DIR="%DSM_DIR%" -DDSM_LOG="%DSM_LOG%" -jar "..\..\..\dsm.jar"
4. The Tivoli Storage Manager GUI is opened and the operation can be performed again.
Note: In case the operation fails again with a freeze increase the heapsize on every attempt with an increment of 64 MB
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21667729