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

CLI APPLICATION MAY TRAP DUE TO MEMORY CORRUPTION

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
An CLI application may trap due to memory corruption. 
In the db2diag.log file you will get message 'Corrupt pool free 
tree node.': 
 
2013-05-23-21.12.34.979000+120 E853648F549          LEVEL: 
Severe 
PID     : 248                  TID : 6996           PROC : 
sample.EXE 
INSTANCE:                      NODE : 000           DB   : 
SAMPLE 
APPID   : 172.25.2.122.58290.130523191234 
HOSTNAME: MYHOST 
EDUID   : 6996 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:999 
MESSAGE : Memory validation failure, diagnostic file dumped. 
DATA #1 : String, 28 bytes 
Corrupt pool free tree node. 
DATA #2 : File name, 28 bytes 
248.6996.mem_diagnostics.txt 
 
2013-05-23-21.12.35.011000+120 I854199F1266         LEVEL: 
Warning 
PID     : 248                  TID : 6996           PROC : 
sample.EXE 
INSTANCE:                      NODE : 000           DB   : 
SAMPLE 
APPID   : 172.25.2.122.58290.130523191234 
HOSTNAME: MYHOST 
EDUID   : 6996 
FUNCTION: DB2 UDB, SQO Memory Management, sqlogmblkEx, 
probe:1000 
MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid 
memory addr" 
          DIA8561C A invalid memory block was encountered. 
DATA #1 : String, 43 bytes 
Memory management block allocation failure. 
DATA #2 : Codepath, 8 bytes 
20:28 
DATA #3 : Memory pool handle pointer, 
PD_TYPE_MEM_POOL_HANDLE_PTR, 8 bytes 
0x0000000003e008f8 
DATA #4 : Requested size, PD_TYPE_MEM_REQUESTED_SIZE, 8 bytes 
19 
DATA #5 : Adjusted block size, PD_TYPE_MEM_ADJUSTED_SIZE, 8 
bytes 
64 
DATA #6 : Options for requested block, PD_TYPE_GET_MEM_OPTIONS, 
4 bytes 
0x00000000 
DATA #7 : Pointer to address that will be set by new allocation, 
PD_TYPE_PTR_TO_ADDRESS_OUT, 8 bytes 
0x00000000043ef488 
DATA #8 : File name, PD_TYPE_OSS_MEM_FILE_NAME, 10 bytes 
sqlesetc.C 
DATA #9 : Line of code, PD_TYPE_OSS_MEM_LINE_NUM, 8 bytes 
2635 
DATA #10: Resource binding pointer, 
PD_TYPE_RESOURCE_BINDING_PTR, 8 bytes 
0x0000000000000000 
 
2013-05-23-21.12.35.073000+120 I855467F492          LEVEL: 
Severe 
PID     : 248                  TID : 6996           PROC : 
sample.EXE 
INSTANCE:                      NODE : 000           DB   : 
SAMPLE 
APPID   : 172.25.2.122.58290.130523191234 
HOSTNAME: MYHOST 
EDUID   : 6996 
FUNCTION: DB2 UDB, base sys utilities, sqlePopulateSetInfoBlk, 
probe:400 
RETCODE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid 
memory addr" 
          DIA8561C A invalid memory block was encountered.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 Fix Pack 9                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 version 9.7 Fix Pack 9
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.06.2013
16.12.2013
16.12.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP9
Problem behoben lt. FixList in der Version
9.7.0.9 FixList
9.7.0.9 FixList