IT08789: ISSUING THE QUERY NODE AND REMOVE NODE COMMANDS MAY RESULT IN A DEADLOCK CONDITION

7.1.3.000-TIV-TSMSRV-WIN
7.1.3.000-TIV-TSMSRV-SolarisSPARC
7.1.3.000-TIV-TSMSRV-Linuxx86_64
7.1.3.000-TIV-TSMSRV-Linuxs390x
7.1.3.000-TIV-TSMSRV-Linuxppc64
7.1.3.000-TIV-TSMSRV-HP-UX
7.1.3.000-TIV-TSMSRV-AIX

APAR status

• Closed as program error.

Error description

• Issuing the QUERY NODE F=D and REMOVE NODE commands at the same
  time may result in a deadlock condition as each command attempts
  to acquire the database lock held by the other command.  Neither
  command will return any data and eventually the commands are
  terminated on the server after the amount of time specified by
  the RESOURCETIMEOUT parameter has elapsed.
  
  Tivoli Storage Manager Versions Affected:
  All supported versions
  
  Customer/L2 Diagnostics:
  The output from the SHOW RESQ command will show one thread
  attempting to acquire lock type 46100 and another thread waiting
  to acquire lock type 17001:
  
     ==========================================================
     This is a local waiter.
     status=resWaiting waitTime=16 minutes
     waiter Type=unknown (0) timeout value=60 minutes
     txnSeqNo=0:190028081 resourceName=(CLIENT) lengthLen=11
     type=17001 and nameSpace=0
     waiter thead id is 331372 condition=372684392
      mutex=281756376 abortFunc=10953278
     ==========================================================
     This is a local waiter.
     status=resWaiting waitTime=16 minutes
     waiter Type=unknown (0) timeout value=60 minutes
     txnSeqNo=0:190027978 resourceName=(*NULL*) lengthLen=0
     type=46100 and nameSpace=0
     waiter thead id is 331374 condition=372680680
      mutex=281756376 abortFunc=10953278
     ==========================================================
  
  The output from the SHOW LOCKS command will show that each of
  the threads is holding a database lock while also trying to
  acquire the lock held by the other thread:
  
     slot -> 1102:
     LockDesc: Type=46100(bf collocation group universe),
     NameSpace=0, SummMode=sLock, Key=''
       Holder: (bfcollut.c:933 Thread 331372) Tsn=0:190027635,
       Mode=sLock
       Waiter: (bfcollut.c:809 Thread 331374) Tsn=0:190027978,
       Mode=xLock
  
     slot -> 1525:
     LockDesc: Type=17001(admin node name), NameSpace=0,
     SummMode=sixLock, Key='CLIENT'
       Holder: (admutil.c:6104 Thread 331374) Tsn=0:190027978,
       Mode=sixLock
       Waiter: (admutil.c:6104 Thread 331372) Tsn=0:190028081,
       Mode=sLock
  
  Initial Impact:
  Low
  
  Additional Keywords:
  ANR2033E ANR0538I resqueue hang
  

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 level 7.1.3. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• The problem was fixed.
  

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

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP