DB2 - Problem description
| Problem IT02677 | Status: Closed |
TRAP IN SQLPKILLIFWAITING AFTER DEADLOCK | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
DB2 might trap with the following stack when there is a
deadlock and at least one of the involved transactions is in
one of these states (shown in db2pd -db <dbname> -transactions
output collected as part of FODC): Prepare (PREP), Abort
(ABORT), Commit (COMMIT), or Rollback to Save Point (SAVEPNT).
0 ossDumpStackTraceInternal
1 ossDumpStackTraceV98
2 OSSTrapFile::dumpEx
3 sqlo_trce
4 sqloEDUCodeTrapHandler
5 __PRETTY_FUNCTION__.6093
6 sqlpKillIfWaiting
7 sqlpCheckAndKillTransaction
8 sqlplLDDResolveLocalDeadlocks
9 sqlpldl
10 sqpLLMEdu::RunEDU
11 sqzEDUObj::EDUDriver
12 sqloEDUEntry
13 pthread_tryjoin_np
14 clone
Note the agent that will be trapping is the deadlock
detector EDU (db2dlock).
EDUNAME: db2dlock (<database_name>) 0
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler,
probe:90
MESSAGE : ADM14011C A critical failure has caused the following
type of error:
"Trap". The DB2 database manager cannot recover from
the failure.
First Occurrence Data Capture (FODC) was invoked in
the following
mode: "Automatic". FODC diagnostic information is
located in the
following directory: | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 and Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
| Solution | |
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.06.2014 16.07.2015 16.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|