home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC79769 Status: Geschlossen

DB2 SERVER MAY HANG AFTER A TRAPPED THREAD IS SUSTAINED

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Without this APAR, customer is exposed to the issue as       * 
* described in the "ERROR DESCRIPTION" section.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7, Fixpack 6.                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 9.7, Fixpack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84274 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.11.2011
18.07.2012
18.07.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList