DB2 - Problembeschreibung
Problem IC62882 | Status: Geschlossen |
DB2 SYSTEM RUNNING IN AN OUT OF MEMORY SITUATION MAY CAUSE INSTANCE CRASH. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
Due to improper setting of memory related parameters, db2 system may run in an out of memory situation. We can see following entries in db2diag.log: 2009-04-21-15.20.24.468000+480 I55822707H607 LEVEL: Severe PID : XXX TID : XXXX PROC : db2syscs.exe INSTANCE: XXX NODE : XXX DB : XXXXXX APPHDL : X-XXXXX APPID: 192.168.249.178.35333.090421072 AUTHID : XXXXXX EDUID : XXXX EDUNAME: db2agent (XXXX) 0 FUNCTION: DB2 UDB, base sys utilities, sqleAllocateDbAppMem, probe:30 RETCODE : ZRC=0x8B0F0014=-1961951212=SQLO_NOMEM_APPSHRH "No memory available in 'Applications Shared Heap'" DIA8300C A memory heap error has occurred. We should prevent db2 system to keep running into an out of memory situation so often. It may cause db2 instance crash. Stack generated in this case: offset: 0000018B in <_sqlofshr.> <sqlomshr.C:5573> offset: 000014DF in <?FirstConnect@sqeLocalDatabase@@QAEXPAUSQLE_BWA@@AADPAVsqeAgent @@PAUsqlo_gmt@@HH@Z> <sqle_database.C:238> offset: 0000036F in <?FirstConnect@sqeLocalDatabase@@QAEXPAUSQLE_BWA@@AADPAVsqeAgent @@PAUsqlo_gmt@@HH@Z> <sqle_database.C:3293> offset: 00000A81 in <?StartUsingLocalDatabase@sqeDBMgr@@QAEXPAUSQLE_BWA@@PAVsqeAgent @@AADDPAUsqlo_gmt@@@Z> <sqle_database_services.C:859> | |
Problem-Zusammenfassung: | |
Users Affected: All user prior to DB2 Version 97 Fix Pack 1. Problem Description: Problem was first fixed in DB2 Version 97 Fix Pack 1. | |
Local-Fix: | |
We can prevent hitting this problem if we do not keep running out of memory. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in DB2 Version 97 Fix Pack 1. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 01.09.2009 02.03.2010 02.03.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP1 | |
Problem behoben lt. FixList in der Version | |
9.7.0.1 |