IC69913: SERVER HALT COMMAND CAN TAKE A LONG TIME TO COMPLETE WHEN RUNNING RUNSTATS ON A LARGE TABLE.

IBM Tivoli Storage Manager (TSM) server V6.1.4.x interim fix downloads

APAR status

• Closed as program error.

Error description

• A Tivoli Storage Manager server halt command can take a long
  
  time to complete, when running runstats on a large table, and
  can use a lot of cpu and will appear to be
  hung.
  
  Customer/L2 Diagnostics:
  
  Forcing a core on the dsmserv process and analysing the crash
  file, one can see from the stack trace that
  a hang will be observed at halt due to a long running runstats
  operation.
  In addition, you should see a thread in RdbMonitorStatsThread
  that initiated both the reorg and the runstats:
  
  #10 0x00002aaaabb0d213 in db2Runstats ()
     from /tiam/IBM_IA_SSAM1/tsm/sqllib/lib64/libdb2.so.1
  #11 0x000000000072709a in RdbRunstatOneTable (
      db2TableName=0x2aaab2470e38 "Archive.Objects",
  myConnP=0x168e1e8,
      commit=True) at tbtbl.c:12080
  #12 0x000000000072865c in RdbReorgRunstatOneTable
  (tInfoP=0x2aaab2470e28,
      myConnP=0x168e1e8) at tbtbl.c:11747
  #13 0x0000000000728b5f in tbiReorgRunstatTbl (
      tblName=0x1374678 "Archive.Objects") at tbtbl.c:7017
  #14 0x0000000000746f52 in RdbMonitorStatsThread (notused=<value
  
  
  Initial Impact:
  Medium
  .
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Server versions 6.1 and 6.2
  .
  Additional Keywords:
  TSM zz61 zz62 halt long hang runstats process reorg hung hacmp
  clustering
  
  | MDVPARTL 6.1.3.3 |
  | MDVPARTL 6.1.4.0 |
  

Local fix

• Allow more time for halt to complete
  
  or
  
  Use the option
  RUNSTATSCHKINTERVAL <interval_between_checks_in_mins>
  in dsmserv.opt to increase the interval between runstats
  to lessen the chance of runstats running at time of halt.
  The value is in minutes, and can be between 10 and 1440
  (the default is 10).
  
  or
  
  Add the following line to the
  dsmserv.opt file to turn off REORG of the db2 database:
  ALLOWREORGTABLE NO
  

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.4.2, 6.1.5, and 6.2.2. 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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP