IC66250: TIVOLI STORAGE MANAGER HANGS AFTER ANR4529I AUTOMATIC DATABASE BACKUP

APAR status

• Closed as program error.

Error description

• TSM server hangs when the internal database backup is started to
  prevent the activelog from filling.
  
  Customer/L2 Diagnostics:
  The last messages in the actlog, before the hang:
  ANR4529I An automatic full or incremental database backup will
  be started. The active log space used is xxx megabytes, and the
  active log space available yy megabytes. The ratio, 0.92,
  exceeds the threshold 0.80.
  ANR4559I Backup DB is in progress.
  ANR0984I Process x for DATABASE BACKUP started in the BACKGROUND
  at ...
  
  Capture a core file by doing a kill -11 on the hung TSM server
  process id.  Core stack information:
  
  #0  0x0000003e6de0a496 in pthread_cond_wait@@GLIBC_2.3.2 ()
     from /lib64/libpthread.so.0
  #1  0x0000000000c7c622 in pkWaitConditionTracked (condP=<value
  optimized out>,
      mutexP=<value optimized out>, abstime=0, file=0xeec44d
  "latch.c", line=253)
      at pkmon.c:879
  #2  0x0000000000bf2d5d in AcquireLatchSpecific
  (latchP=0x4643750, mode=sLatch,
      mutexP=0x4643568, requestor=0xdd0eae "dbiconn.c") at
  latch.c:253
  #3  0x000000000071ae3c in DbiGetConnection () at dbiconn.c:1456
  #4  0x0000000000718bbd in dbInitThread () at dbiinit.c:431
  #5  0x0000000000c7bb9d in pkBeginNamedThread (funcP=0x714950
  <IcBackupThread>,
      argP=0x2aaba44edc30, priority=<value optimized out>,
  threadIdP=0x42636d7c,
      nameP=0xdcf4d5 "IcBackupThread") at pkthread.c:858
  #6  0x0000000000715dc3 in icStartBackup (fullBackup=False,
  incremental=True,
      snapshot=<value optimized out>, scratch=True,
      className=0x46511c4 "PRIMARY_POOL_KRC", resolvedVolList=0x0,
  volCount=0,
      schedName=0x0, foregroundStream=0xfffffffffffffffc,
  procIdP=0x42636f28,
      threadIdP=0xfffffffffffffffc) at icback.c:575
  
  Initial Impact: Medium
  
  Additional Keywords: hung data base auto zz61
  

Local fix

• Increase the Activelogsize in the dsmserv.opt. The max in MB is:
  131072. Then do more scheduled DB backups.
  Also set  "ALLOWREORGTABLE NO" in the dsmserv.opt,  If the
  Activelog still exceeds the threshold, the internal  database
  backup will be started and cause another hang.
  Get to fixing level
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users.     *
  ****************************************************************
  * PROBLEM DESCRIPTION: See error description.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be         *
  *                 fixed in levels 6.1.3.2. and 6.1.4.0. Note   *
  *                 that this is subject to change at the        *
  *                 discretion of IBM.                           *
  ****************************************************************
  *
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Sun Solaris,
  Linux, and Windows.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R61A PSY

     UP

• R61H PSY

     UP

• R61L PSY

     UP

• R61S PSY

     UP

• R61W PSY

     UP