|
Problem IC98997
|
Status: Closed |
IN PURESCALE ENVIRNMENT, 3-WAY DEADLATCH COULD HAPPEN IN RARE TIMING SCENARIO. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In rare timing scenario, 3-way deadlatch among
SQLO_LT_SQLB_BPD__bpdLatch_SX and
SQLO_LT_SQLD_PAGE_CACHE__pageCacheLatch and
SQLO_LT_SQLD_TCB__loadInProgress could happen. This can only
happen on pureScale environment.
This can be hit when the following 2 situation happens at the
same time;
1) Multiple sessions are accessing the same table.
2) The TCB of the index of the table being accessed is being
reloaded because its definition is changed on the remote node.
SQLO_LT_SQLB_BPD__bpdLatch_SX is an untrackable latch so we
cannot determine this 3-way deadlatch using stacks or db2pd
-latches output. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL PURESCALE USERS *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix *
* Pack 4) *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix
Pack 4) |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.01.2014
07.10.2014
07.10.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
