| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT37537 | Status: Closed |
ON DB2/AIX, POST FROM THREAD_POST CAN BE SKIPPED/DEFERRED BY WAITER INTERRUPTED IN THREAD_WAIT , LEADING TO PANIC/SHUTDOWN | |
| product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
| Problem description: | |
A timing hole in db2's synchronization implementation on AIX can
lead to an abnormal shutdown when a waiter is interrupted by a
force/signal.
A variety of symptoms could occur, but one common symptom is an
ESRCH error resulting in a panic.
Eample db2diag.log entry :
EDUID : 5399 EDUNAME: db2pfchr (TEST1) 0
FUNCTION: DB2 UDB, SQO Latch Tracing,
SQLO_SLATCH_CAS64::releaseConflict, probe:340
CALLED : OS, -, unspecified_system_function
OSERR : ESRCH (3) "No such process"
DATA #1 : String, 13 bytes
post error!:
DATA #2 : File name, 16 bytes
sqloLatchCAS64.C
DATA #3 : Source file line number, 8 bytes
1089
DATA #4 : Codepath, 8 bytes
2:6:8:20:22:26
DATA #5 : String, 126 bytes
0x0000000004010000: {
held X: 1
reserved for X: 0
shared holders: 0
firstSharIndex: 0x40
firstExclIndex: 0x0
example stack
sqle_panic__Fi
dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T
3T7
releaseConflict__17SQLO_SLATCH_CAS64Fv
sqlbReadAndReleaseBuffers__FP16SQLB_OBJECT_DESCUiUlN23P11SQLB_pf
Misc
demangled:
sqle_panic
SQLO_SLATCH_CAS64::dumpDiagInfoAndPanic
SQLO_SLATCH_CAS64::releaseConflict
sqlbReadAndReleaseBuffers | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * On AIX * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.6 or higher * **************************************************************** | |
| Local Fix: | |
| Solution | |
| Workaround | |
**************************************************************** * USERS AFFECTED: * * On AIX * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.5.6 or higher * **************************************************************** | |
| Comment | |
First fixed in Db2 11.5.6 | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.07.2021 21.07.2021 21.07.2021 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
