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 IC80290 Status: Geschlossen

INSTANCE CRASH WITH SEGV (SEGMENTATION VIOLATION) IN FUNCTION
SQLPGETANDPROCESSGRAPHS()

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
On systems running Workload Management (WLM), the 
deadlock detector may trigger a crash due to a segv (signal 11). 
 
The following message will be reported in the db2diag.log: 
 
--------------------------------------- 
2011-11-02-22.57.00.365968-240 I844276694A396     LEVEL: Warning 
PID     : 622978               TID  : 4674        PROC : db2sysc 
0 
INSTANCE: <inst-name>             NODE : 000 
EDUID   : 4674                 EDUNAME: db2glock (<db-name>) 0 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:600 
DATA #1 : String, 27 bytes 
 sqlpGetAndProcessGraphs__F 
DATA #2 : String, 4 bytes 
sqlp 
--------------------------------------- 
 
The following stack is reported: 
------------------------------------------ 
Signal #11 
 
0x090000000B1625DC 
sqlpGetAndProcessGraphs__FP16sqeLocalDatabaseP8SQLP_LCBPUlPUi + 
0x90 
0x090000000B160070 sqlplgdd__FPcUi + 0x598 
0x090000000CCA5330 sqloEDUEntry + 0x18 
-----------------------------------------
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using Work Load Manager (WLM)                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* On systems running Workload Manager (WLM), the deadlock      * 
* detector may trigger a crash due to a segv (signal 11).      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* To avoid experiencing this issue users can upgrade to DB2    * 
* Version V9.7 fix pack 6 at the minimum.                      * 
****************************************************************
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 V9.7 fix pack 6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.12.2011
18.06.2012
18.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList