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

DUMPSHM OPTION FOR DB2FODC MAY MISS MUCH OF SHARED MEMORY FOR
CONFIGURATIONS LARGER THAN 4GB

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When the new compact shared memory dump option is set 
(DB2FODC="DUMPSHM=ON") and DB2 abends, DB2 dumps significant 
areas of shared memory to a a binary dump file in the FODC 
folder.  When the configuration of a memory set is larger than 
4GB (the most common case being database memory), important 
portions of shared memory may be missed.  This may result in 
support being unable to determine the root cause for the abend.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All UNIX systems are vulnerable                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* This issue affects a serviceability feature only.  Upgrade   * 
* to DB2 Version 10.5 Fix Pack 7                               * 
****************************************************************
Local-Fix:
avoid using the DUMPSHM option - used in conjunction with 
CORESHM=NO.  Rely on the default full coredump behaviour (do not 
set CORESHM=NO).
Lösung
Problem first fixed in DB2 Version 10.5 Fix Pack 7
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.07.2015
16.02.2016
16.02.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList