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

INSTANCE MAY TRAP DURING SNAPSHOT INVOCATION DUE TO MEMORY EXHAUSTION
CAUSING MEMORY ALLOCATION ERRORS.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
An out of memory condition may result in snapshot monitor to 
trap the instance with below messages and a stack resembling: 
 
2009-02-25-12.35.36.802682-360 E1255562A729       LEVEL: Warning 
PID     : 172804               TID  : 56549       PROC : db2sysc 
4 
INSTANCE: xxxx1             NODE : 004         DB   : xx 
 
APPHDL  : 0-49278              APPID: xxxx.A36A.0CEED5163606 
AUTHID  : xxxx 
EDUID   : 56549                EDUNAME: db2agntp (xx) 4 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloMemLogPoolConditions, probe:30 
DATA #1 : <preformatted> 
Out of memory failure for Sort Heap on node 4. 
Requested block size           : 4000 bytes. 
Physical heap size             : 1091633152 bytes. 
Configured heap size           : 281474976645120 bytes. 
Unreserved memory used by heap : 0 bytes. 
Unreserved memory left in set  : 0 bytes. 
 
2009-02-25-12.35.36.822560-360 I1256292A451       LEVEL: Error 
PID     : 172804               TID  : 56549       PROC : db2sysc 
4 
INSTANCE: xxxx             NODE : 004         DB   : xx 
 
APPHDL  : 0-49278              APPID: GA640A4B.A36A.0CEED5163606 
AUTHID  : xxxxx 
EDUID   : 56549                EDUNAME: db2agntp (xx) 4 
FUNCTION: DB2 UDB, runtime interpreter, sqlri_hsjnGetTupleBlock, 
probe:10 
MESSAGE : Virtual memory exhausted 
 
Stacks: 
0x0900000000358708 pthread_kill + 0x88 
0x0900000000358144 _p_raise + 0x5C 
0x0900000000056AC0 raise + 0x34 
0x0900000000082004 abort + 0xB4 
0x0900000002F5A1C8 sqloExitEDU + 0x228 
0x0900000002F33C00 sqle_panic__Fv + 0x180 
0x0900000002F48A78 sqloSpinLockReleaseConflict + 0x298 
0x09000000033F0E60 turn_off_switches__16sqm_agent_entityFPUi + 
0x8A0 
0x09000000033EEB88 update_switches__10sqm_entityFPUiR9sqm_scope 
+ 0x128 
0x090000000342B8A8 destroy_me__11sqm_controlFP10sqm_entity + 
0x68 
0x090000000342B604 remove_me__11sqm_controlFP10sqm_entityb + 
0x344 
0x0900000003438424 TermApplication__14sqeApplicationFv + 0x4C4 
0x090000000326C890 
DestroyAppl__14sqeAppServicesFP14sqeApplication + 0x5D0 
0x09000000054B250C sqleProcessSubRequest__FP8sqeAgent + 0x58C 
0x0900000003036EE8 RunEDU__8sqeAgentFv + 0x928 
0x09000000031FFCC4 EDUDriver__9sqzEDUObjFv + 0x1E4
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Snpahot Monitor                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An out of memory condition may occur with snapshot           * 
* monitoring causing a trap of the instance.                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 FP1.                                          * 
****************************************************************
Local-Fix:
There is no local fix, and the APAR should be applied to resolve 
the issue.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Due to a timing scenario in a panic may ensue
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.10.2009
17.02.2010
17.02.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList