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

HITTING INSTANCE MEMORY LIMIT SHOULD NOT BRING DOWN THE DATABASE

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
Instance Memory limits are not intended to be enforced where 
enforcing the limit would result in bringing down the database 
i.e. "database marked bad".  However, currently, Instance Memory 
allocation failures in the deadlock detector and global deadlock 
detector will have this effect. 
Connections will be forced off, and the database will be 
recycled requiring crash recovery. 
 
This APAR will allow allocations from these EDUs to exceed the 
Instance Memory limit.  Note that memory allocation failures due 
to other reasons (eg. Operating System limits) will still cause 
the database to be recycled. 
 
db2diag.log entries include: 
2009-11-30-10.40.52.636927-360 I5534792E511        LEVEL: Error 
PID     : 16939                TID  : 183307856224 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
EDUID   : 30                   EDUNAME: db2dlock (SAMPLE) 0 
FUNCTION: DB2 UDB, lock manager, sqlpldl, probe:815 
MESSAGE : Not able to allocate memory for ldd matrix from db 
shared heap. total 
          matrix size: 
DATA #1 : Hexdump, 8 bytes 
0x0000002AADFFDD20 : 00B0 4000 0000 0000 
..@..... 
 
2009-11-30-10.40.52.637028-360 I5535304E444        LEVEL: Error 
PID     : 16939                TID  : 183307856224 PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE 
EDUID   : 30                   EDUNAME: db2dlock (SAMPLE) 0 
FUNCTION: DB2 UDB, lock manager, sqlpldl, probe:815 
MESSAGE : Dead Lock Detector error: 
DATA #1 : Hexdump, 8 bytes 
0x0000002AADFFDDE8 : 7700 1080 0200 0F8B 
w.......
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Systems with enforced Instance Memory limit.                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Increase Instance Memory setting or reduce DB2               * 
* memoryrequirements                                           * 
****************************************************************
Local-Fix:
Consider using the AUTOMATIC setting for Instance Memory or 
increasing the Instance Memory limit
verfügbare FixPacks:
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
Problem first fixed in DB2 Version 9.5 Fix Pack 6
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC65076 IC66428 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
10.12.2009
22.06.2010
22.06.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version