DB2 - Problem description
Problem IC84274 | Status: Closed |
DB2 SERVER MAY HANG AFTER A TRAPPED THREAD IS SUSTAINED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
DB2 server may hang after DB2 sustains a trapped thread. The db2diag.log may contain entries like the following: 2011-10-30-16.57.58.035757-240 I14561153A541 LEVEL: Severe PID : 840548 TID : 14737 PROC : db2sysc 2 ... FUNCTION: DB2 UDB, RAS/PD component, pdResilienceIsSafeToSustain, probe:800 DATA #1 : String, 37 bytes Trap Sustainability Criteria Checking DATA #2 : Hex integer, 8 bytes 0x0000000400003001 DATA #3 : Boolean, 1 bytes true ... 2011-10-30-16.57.58.058740-240 E14583194A946 LEVEL: Severe PID : 840548 TID : 14737 PROC : db2sysc 2 ... (suspended) FUNCTION: DB2 UDB, DRDA Application Server, sqljsTrapResilience, probe:800 MESSAGE : ADM14013C The following type of critical error occurred: "Trap". This error occurred because one or more threads that are associated with the current DB2 instance have been suspended, but the instance process is still running. 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 10.1 FP1 or subsequent fix pack. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 Version 10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.06.2012 17.01.2013 17.01.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |