IT04115: LARGE RESTORE USING BACKUP-ARCHIVE CLIENT GUI MAY HANG

IBM Tivoli Storage Manager (TSM) Client 7.1.2 Downloads and READMEs
IBM Tivoli Storage Manager Client 6.4.3 Downloads and READMEs
IBM Tivoli Storage Manager (TSM) client 6.3.2.x interim fix downloads - EOL

APAR status

• Closed as program error.

Error description

• When a restore of large number of objects, such as PIT restore
  of 500.000 files, is initiated using Backup-Archive GUI, the
  client may hang. This can be caused due to exhausted Java heap
  space.
  
  Entries similar to following can be observed in the dsmj.log:
  
  java.lang.NoClassDefFoundError: com.ibm.oti.util.Msg
  (initialization failure)
   at java.lang.J9VMInternals.initialize(J9VMInternals.java:176)
   at
  java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:776)
   at
  java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:770)
   at java.lang.Thread.uncaughtException(Thread.java:1285)
  Caused by: java.lang.OutOfMemoryError: Java heap space
   at java.util.Hashtable.put(Hashtable.java:569)
   at java.util.Properties.load0(Properties.java:406)
  
  TSM Versions Affected:
  Tivoli Storage Manager client on Windows platform
  
  Initial Impact:
  Low
  
  Additional Keywords:
  TSM client GUI hang restore OutOfMemoryError Java heap space
  

Local fix

• Starting from versions 6.1.5 and 6.2.3 dsm.exe accepts JVM -X
  parameter. In following example client GUI has been started from
   command line with -Xmx2048m parameter, which increases Java
  heap size to 2 GB.
  
  dsm.exe -Xmx2048m
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Backup-archive client versions 6.3, 6.4      *
  *                 and 7.1 on all platforms.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in levels 6.3.2.3, 6.3.2.4, 6.4.3, and 7.1.2.*
  *                 Note: this is subject to change at the       *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• The problem described in this APAR has been fixed so that it
  no longer occurs.
  

Temporary fix

• 6.3.2.3 (UNIX and Linux clients) and 6.3.2.4 (Windows clients)
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• DSM
  

Fix information

• Fixed component name

  TSM CLIENT

• Fixed component ID

  5698ISMCL

Applicable component levels

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63M PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R64A PSY

     UP

• R64H PSY

     UP

• R64L PSY

     UP

• R64M PSY

     UP

• R64S PSY

     UP

• R64W PSY

     UP

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71M PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP