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

Cleanup code triggered by out of memory conditions in DB2 monitoring
area can crash the instance.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
DB2 instance can crash when there are out of memory conditions 
in monitoring area. This can happen if an attempt is made to 
unlatch an unlocked latch during cleanup and after the holder 
of the latch has been freed.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Out of memory condition                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Out of memory condition can crash db2                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install DB2v9.5 fp6                                          * 
****************************************************************
Local-Fix:
Increase Database Monitor Heap
verfügbare FixPacks:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
DB2v9.5 fp6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
12.11.2009
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version