IBM Support

IC96006: EXPIRE INVENTORY PROCESS CAN HANG WHEN INITIATED WITH WAIT=YES P ARAMETER.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The Tivoli Storage Manager inventory expiration process can
    hang under rare conditions when initiated with the WAIT=YES
    parameter.  This is a timing specific condition which
    can cause a resource deadlock.
    
    Users may observe that the EXPIRE INVENTORY process is hung.
    Also other QUERY and UPDATE commands can hang simultaneously,
    like QUERY NODE, UPDATE COPYGROUP, QUERY COPYGROUP, etc.
    
    The hung EXPIRE INVENTORY process should eventually succumb
    to the RESOURCETIMEOUT, which should clear the hung processes.
    
    Customer/L2 Diagnostics:
    Use SHOW THREADS, pstack/procstack, or force a coredump to
    review the the active thread callstacks.
    
    If this APAR is a match, a thread for imStartExpiration should
    be in a condition wait, similar to the following:
    
      pth_cond._cond_wait_global()
      pth_cond._cond_wait()
      pth_cond.pthread_cond_wait()
      pkmon.pkWaitConditionTracked()    <----------
      imdmgr.imStartExpiration()        <----------
      ...
    
    Also, an ExpirationProcessThread should be in a condition
    wait, including the pmLockUniverse() function similar to
    the following:
    
      pth_cond._cond_wait_global()
      pth_cond._cond_wait()
      pth_cond.pthread_cond_wait()
      pkmon.pkWaitConditionTracked()   <----------
      tmlock.tmLockTracked()
      pmutil.PmLockUniverse()          <----------
      pmcache.pmOpenDomain()
      imdmgr.ExpirationProcessThread() <----------
      pkthread.StartThread()
    
    Finally, there could be one or more threads also in a wait
    condition that contain the the sane pmLockUniverse() function.
    The following example is one such thread for a hung QUERY
    NODE command:
    
      pth_cond._cond_wait_global()
      pth_cond._cond_wait()
      pth_cond.pthread_cond_wait()
      pkmon.pkWaitConditionTracked()   <----------
      tmlock.tmLockTracked()
      pmutil.PmLockUniverse()          <----------
      pmdom.pmMatchDomains()
      admnode.AdmQueryNode()           <----------
      ...
    
    Initial Impact:
    High
    
    Tivoli Storage Manager Versions Affected:
    All V6 Tivoli Storage Manager server users
    
    Additional Keywords:
    TSM HANG HUNG EXPIRATION EXPIRE INVENTORY WAIT NODE COPYGROUP
    

Local fix

  • Run expiration without the WAIT=YES parameter.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All Tivoli Storage Manager server users      *
    *                 specifying the WAIT=YES parameter on the     *
    *                 EXPIRE INVENTORY command.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: See error description.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available. This      *
    *                 problem is currently projected to be fixed   *
    *                 in levels 6.3.5 and 7.1.1. Note that this    *
    *                 is subject to change at the discretion of    *
    *                 IBM.                                         *
    ****************************************************************
    *
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IC96006

  • Reported component name

    TSM SERVER

  • Reported component ID

    5698ISMSV

  • Reported release

    63A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-17

  • Closed date

    2014-01-03

  • Last modified date

    2014-01-03

  • 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

  • R63A PSY

       UP

  • R63H PSY

       UP

  • R63L PSY

       UP

  • R63S PSY

       UP

  • R63W PSY

       UP

  • R71A PSY

       UP

  • R71H PSY

       UP

  • R71L PSY

       UP

  • R71S PSY

       UP

  • R71W PSY

       UP



Document information

More support for: Tivoli Storage Manager

Software version: 63A

Reference #: IC96006

Modified date: 03 January 2014