IC69507: DEADLOCK WHEN MULTIPLE NODES BACKUP TO THE SAME ACTIVE DATA POOL

APAR status

• Closed as program error.

Error description

• Following deadlock may occurs when nodes are saving data to ADP
  
  ANR0379W A server database deadlock situation has been
       encountered; the lock request for the as volume id lock,
       will be denied to resolve the deadlock
  
  In the case traced, the deadlock was caused by two transactions
  "44641094", "44641114"
   44641094 is started by schedule "SCHED1", and 44641114 is
  started by schedule "SCHED2".
   txn 44641094 acquired volume 990's lock for the reason of
  allocation and waited volume 1470's lock for deallocation.
  While 44641114 acquired volume 1470's lock for allocation
  and waited volume 990's lock for deallocation.
   Both of volumes are from Active Data Pool.
  
  Tivoli Storage Manager Versions Affected:
  
  5.4 , 5.5  , 6.1 , 6.2
  
  Customer/L2 Diagnostics :
  
  - Extract from actlog
  
  A Deadlock was found:
  Transaction 0:44641094.
    Waiting for Lock mode xLock on: Type=36002(as volume
   id), NameSpace=1470, Key=''
    Held by transaction 0:44641114 in mode xLock.
  Transaction 0:44641114.
    Waiting for Lock mode xLock on: Type=36002(as volume
   id), NameSpace=990, Key=''
    Held by transaction 0:44641094 in mode xLock.
   Lock hash table contents (slots=510):
  ANR0379W A server database deadlock situation has been
   encountered; the lock request for the as volume id lock,
   will be denied to resolve the deadlock.
  ANR1181E astxn.c(729): Data storage transaction 0:44641094
   was aborted. (SESSION: 3583)
  
  
  Initial Impact: Medium
  
  Additional Keywords:
  AS_LOCK_VOLID ADP
  

Local fix

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 5.5.6, 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, Windows,
  and z/OS.
  

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

• R61Z PSY

     UP

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R62Z PSY

     UP