LI71846: DB2 hang due to agent looping inside the sqliTryToCleanup, sqliTestDeletedMDCRidLock functions.

DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 2a - interim special build 2a
DB2 Version 9.1 Fix Pack 6   for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 3a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• The symptom is a hang encountered with callstack indicating that
  an agent is looping inside the sqliTryToCleanup,
  sqliTestDeletedMDCRidLock code path.
  
  This problem can affect any type of table (including MDC, range
  partitioned, XML).  If the APAR fix is not applied, users could
  experiencing a hang.
  
  Here's a sample of the callstacks taken at different time -
  
  [1st iteration]
  sqlichat + 0x0165
  sqliTestDeletedMDCRidLock + 0x09be
  sqliTestDeletedMDCRidLock + 0x1aa9
  sqliTryToCleanup + 0x0176
  ...
  
  [2nd iteration]
  sqliTestDeletedMDCRidLock + 0x09a0
  sqliTestDeletedMDCRidLock + 0x1aa9
  sqliTryToCleanup + 0x0176
  ...
  
  [3rd iteration]
  sqliTestDeletedMDCRidLock + 0x1298
  sqliTryToCleanup + 0x0176
  ...
  
  [4th iteration]
  sqliInitFirstInfo + 0x001f
  sqliTestDeletedMDCRidLock + 0x098d
  sqliTestDeletedMDCRidLock + 0x1aa9
  sqliTryToCleanup + 0x0176
  ...
  
  [5th iteration]
  sqliTestDeletedMDCRidLock + 0x09f3
  sqliTestDeletedMDCRidLock + 0x1aa9
  sqliTryToCleanup + 0x0176
  ...
  

Local fix

Problem summary

• Users affected:
  All Users. This problem can affect any type of table (including
  MDC, range partitioned, XML).
  
  Problem Description:
  If this APAR fix is not applied, users could experiencing a hang
  symptom as described in the "Error Description".
  
  Problem Summary: See "Error Description".
  

Problem conclusion

• First fixed in DB2 UDB Version 9.1, FixPak 3.
  

Temporary fix

• n/a
  

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

  DB2 UDE ESE LIN

• Fixed component ID

  5765F4104

Applicable component levels

• R910 PSY

     UP