DB2 FOR LUW / DB2FORLUW / 970 - DB2

If some tables are defined in the same tablespaces including 
data and indexes, HPU might hang because of a internal deadlatch 
problem when running in parallel on those tables. 
 
You will find an UOW-Executing CoorEDUID by db2pd.inst.alldbs of 
"db2fodc -hang". 
--- 
Applications: 
Address            AppHandl [nod-index] NumAgents  CoorEDUID 
Status                  ... 
0x0780000000910080 206592   [003-09984] 1          18947 
UOW-Executing           ... 
--- 
 
The associated trap file, 7864472.18947.003.stack.txt may have 
below. 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x09000000000EE6F8 thread_wait + 0x98 
0x09000000133E19C0 getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 
0x32C 
0x09000000133E1CC0 getConflict__17SQLO_SLATCH_CAS64FCUl + 0x7C 
0x09000000133E1D88 getConflict__17SQLO_SLATCH_CAS64FCUl@glueFD + 
0x74 
0x090000000F11BE28 sqlbReadPageInternal + 0x20 
0x09000000133ED61C sqlbReadPage + 0x174 
0x09000000133F9488 
.sqlbGetPageFromDisk.fdpr.clone.2060__FP11SQLB_FIX_CBi + 0x118 
0x09000000133FCE48 @72@26456@sqlbFixPage__FP11SQLB_FIX_CBiUiT2 + 
0xCC0 
... 
<LatchInformation> 
Waiting on latch type: (SQLO_LT_SQLB_POOL_CB__readLatch) - 
Address: (77000009bc59a98), Line: 1632, File: sqlbpacc.C 
Holding Latch type: (SQLO_LT_SQLB_POOL_CB__readLatch) - Address: 
(77000009bc59a98), Line: 1632, File: sqlbpacc.C HoldCount: 2 
Holding Latch type: (SQLO_LT_SQLD_TCB__loadInProgress) - 
Address: (77000009ea2e7b8), Line: 6914, File: sqldtcb.C 
HoldCount: 1 
</LatchInformation> 
... 
 
The associated CoorEDUPD can be seen at the db2pd.inst.alldbs of 
"db2fodc -hang" as below. 
-------------------------- 
Application : 
  Address :                0x0780000000910080 
  AppHandl [nod-index] :   206592   [003-09984] 
  TranHdl :                n/a 
  Application PID :        36962360 
  Application Node Name :  xxxxx 
  IP Address:              n/a 
  Connection Start Time :  (1321373164)Wed Nov 16 01:06:04 2011 
  Client User ID :         db2 
  System Auth ID :         DB2 
  Coordinator EDU ID :     18947 
 
  Coordinator Partition :  3 
  Number of Agents :       1 
  Locks timeout value :    NotSet 
  Workload ID :            1 
  Workload Occurrence ID : 2 
  Trusted Context :        n/a 
  Connection Trust Type :  non trusted 
  Role Inherited :         n/a 
 
  Application Name :       db2hpum_debug64 
  Application ID :         *N3.db2.111115160606 
--------------------------

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 6.                            * 
****************************************************************

Using separate data and index tablespaces for different tables 
can work around the problem.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 9.7 FixPack 6.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC83399 IC84348 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.12.2011
06.06.2012
06.06.2012

9.7.FP6