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

PD_GET_DIAG_HIST MAY HIT ERROR "DIA8301C NO MEMORY AVAILABLE IN THE
APPLICATION HEAP"

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Using PD_GET_DIAG_HIST to collect db2diag.log messages might 
result in memory error SQL0954C. 
 
DB2 takes up to 20% of configured INSTANCE_MEMORY for the 
internal memory buffer used to process the db2diag.log entries. 
On systems with large db2diag.log files this might result in 
exceeding the instance memory limits and cause "No memory 
available in 'Application Heap'" errors. 
 
In the db2diag.log you will see a number of messages like the 
following indicating that we are failing to allocated the 
application memory: 
 
2013-06-05-16.30.30.530061+120 I3555773E984          LEVEL: 
Warning 
PID     : 59262                TID : 140664037697280 PROC : 
db2sysc 0 
INSTANCE: db2inst              NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-29689              APPID: 
*LOCAL.db2inst.130605143001 
AUTHID  : db2inst              HOSTNAME: myhost 
EDUID   : 3950                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
SqloMemController::requestMemory, probe:50 
MESSAGE : ZRC=0x8B0F0000=-1961951232=SQLO_NOMEM "No Memory 
Available" 
          DIA8300C A memory heap error has occurred. 
DATA #1 : String, 28 bytes 
Attempt to get memory failed 
DATA #2 : unsigned integer, 8 bytes 
10149036032 
DATA #3 : unsigned integer, 8 bytes 
0 
DATA #4 : String, 13 bytes 
APPL-SAMPLE 
DATA #5 : unsigned integer, 8 bytes 
5281218560 
DATA #6 : unsigned integer, 8 bytes 
0 
DATA #7 : unsigned integer, 8 bytes 
89732939776 
DATA #8 : unsigned integer, 8 bytes 
94468833280 
DATA #9 : unsigned integer, 8 bytes 
0 
 
 
And finally the following messages are printed in the 
db2diag.log: 
 
2013-06-05-16.30.30.535400+120 E3570986E779          LEVEL: 
Warning 
PID     : 59262                TID : 140664037697280 PROC : 
db2sysc 0 
INSTANCE: db2inst              NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-29689              APPID: 
*LOCAL.db2inst.130605143001 
AUTHID  : db2inst              HOSTNAME: myhost 
EDUID   : 3950                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloMemLogPoolConditions, probe:30 
DATA #1 : <preformatted> 
Out of memory failure for Application Heap (APPLHEAPSZ) on node 
0. 
Requested block size           : 10148970472 bytes. 
Physical heap size             : 5074714624 bytes. 
Configured heap size           : 16777216 bytes. 
Unreserved memory used by heap : 0 bytes. 
Unreserved memory left in set  : 0 bytes. 
 
2013-06-05-16.30.30.535569+120 I3571766E669          LEVEL: 
Error 
PID     : 59262                TID : 140664037697280 PROC : 
db2sysc 0 
INSTANCE: db2inst              NODE : 000            DB   : 
SAMPLE 
APPHDL  : 0-29689              APPID: 
*LOCAL.db2inst.130605143001 
AUTHID  : db2inst              HOSTNAME: myhost 
EDUID   : 3950                 EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, WLM, sqlrwExpandableBuffer::addElement, 
probe:10 
CALLED  : DB2 UDB, WLM, sqlrwExpandableBuffer::addElement 
RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
          DIA8301C No memory available in the application heap.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 FIxpack 3 or Higher                 * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First Fixed in DB2 LUW v10.5 Fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.09.2013
27.02.2014
27.02.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList