|
Problem IC90039
|
Status: Closed |
DEADLATCH DURING MEMBER CRASH RECOVERY IN A DB2 PURESCALE ENVIRONMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
During crash recovery of a member in a DB2 pureScale cluster,
there is a small timing window that can result in a deadlatch
between the member and an agent running RUNSTATS on another
member in the cluster. If the deadlatch happens it causes the
crash recovery to hang. The related stacks would show as
follows:
Stack 1:
sqlbFixPage
sqliRefreshInfoPage
sqliIP_CreatePage
sqliIP_FixPage
sqliHardenJITS
sqldHardenJitsForAllIndexes
sqlrLocalRunstats
Stack 2:
sqldLatchIndexes
sqldInitIndexValidityLotch
sqldAllocEmptyTCB
...
sqlpParallelRecovery |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 pureScale Environments *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.3. *
**************************************************************** |
| Local Fix: |
Use the FORCE APPLICATION command to force the application
performing RUNSTATS off the system. This will allow member
crash recovery to complete. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
The problem is first fixed in DB2 version 10.1.0.3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.02.2013
27.09.2013
27.09.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
