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

DB2 INSTANCE CRASHED DUE TO DOUBLE FREEING A MEMORY BLOCK IN THE SHARED
APPLICATION CONTROL HEAP

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Due to overflow of an internal field with 16bit size, DB2 might 
be attempting to double free a memory block during cleanup of 
dynamic SQL workspace in the shared application control heap. 
This would cause the instance crash and following memory 
corruption messages would be reported in the db2diag.log. There 
might be more than one agent reporting the memory corruption on 
the same memory block around the same time. 
 
2009-12-07-22.52.51.907977+540 I18915964A1892     LEVEL: Severe 
PID     : 1355976              TID  : 5147        PROC : db2sysc 
0 
INSTANCE: db2inst1          NODE : 000         DB   : DB1 
APPHDL  : 0-25675              APPID: 127.0.0.1.45365.1512140106 
AUTHID  : db2inst1 
EDUID   : 5147                 EDUNAME: db2agent (DB1) 0 
FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:10 
MESSAGE : Possible memory corruption detected. 
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes 
0x820F0002 
DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8 
bytes 
0x0700000026644040 
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
0x0700000026644028 : FAB0 7000 0002 6640 4152 9011 027D 482C 
..p...f@AR...}H, 
0x0700000026644038 : FAB0 7000 0002 6640 
..p...f@ 
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
0x0700000026644040 : 0000 0000 0000 0000 0224 0000 0000 0000 
.........$...... 
0x0700000026644050 : 0700 0000 1001 1CA0 0700 0000 223B B940 
............";.@ 
0x0700000026644060 : 0000 0000 0000 0000 0000 3A18 00AC 0000 
..........:..... 
CALLSTCK: 
  [0] 0x0900000004263D18 pdLog + 0x88 
  [1] 0x0900000004753A00 
@78@sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0xE8 
  [2] 0x090000000475384C 
sqloDiagnoseFreeBlockFailure__FP8SMemFBlk@glue687 + 0x74 
  [3] 0x09000000040295D4 sqlofmblkEx + 0x458 
  [4] 0x090000000471D28C 
sqlra_sqlW_mem_free_sibling_list__FP8sqlrr_cbP23sqlra_workspace_ 
siblingPUl 
+ 0x870 
  [5] 0x09000000047261B0 
sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli + 0x420 
  [6] 0x0900000004725CC4 
sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli@glueFF3 + 0x74 
  [7] 0x0900000005E31704 
sqlra_sqlW_check_for_cleanup__FP8sqlrr_cbUlP7OSSTick + 0x60 
  [8] 0x0900000004724614 
sqlra_sqlW_get_dynamic_section__FP8sqlrr_cbP16sqlra_cached_var + 
0x1188 
  [9] 0x09000000067C9E6C 
sqlra_load_var__FP8sqlrr_cbP16sqlra_cached_var + 0x468
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users executing a dynamic SQL causing cleanup of dynamic     * 
* SQLworkspace in the shared application control heap          * 
* andoverflow of an internal field with 16bit size.            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Due to overflow of an internal field with 16bit size,        * 
* DB2mightbe attempting to double free a memory block during   * 
* cleanupofdynamic SQL workspace in the shared application     * 
* controlheap.This would cause the instance crash and          * 
* following memorycorruption messages would be reported in the * 
* db2diag.log.Theremight be more than one agent reporting the  * 
* memory corruptiononthe same memory block around the same     * 
* time.2009-12-07-22.52.51.907977+540 I18915964A1892           * 
* LEVEL:SeverePID    : 1355976              TID  : 5147        * 
* PROC :db2sysc0INSTANCE: db2inst1          NODE : 000         * 
* DB  : DB1APPHDL  : 0-25675                                   * 
* APPID:127.0.0.1.45365.1512140106AUTHID  : db2inst1EDUID  :   * 
* 5147                EDUNAME: db2agent (DB1) 0FUNCTION: DB2   * 
* UDB, SQO Memory Management,sqloDiagnoseFreeBlockFailure,     * 
* probe:10MESSAGE : Possible memory corruption detected.DATA   * 
* #1 : ZRC, PD_TYPE_ZRC, 4 bytes0x820F0002DATA #2 : Corrupt    * 
* block address, PD_TYPE_CORRUPT_BLK_PTR,                      * 
* 8bytes0x0700000026644040DATA #3 : Block header,              * 
* PD_TYPE_BLK_HEADER, 24 bytes0x0700000026644028 : FAB0 7000   * 
* 0002 6640 4152 9011 027D                                     * 
* 482C..p...f@AR...}H,0x0700000026644038 : FAB0 7000 0002      * 
* 6640..p...f@DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 * 
* bytes0x0700000026644040 : 0000 0000 0000 0000 0224 0000 0000 * 
* 0000.........$......0x0700000026644050 : 0700 0000 1001 1CA0 * 
* 0700 0000 223B B940............";.@0x0700000026644060 : 0000 * 
* 0000 0000 0000 0000 3A18 00AC                                * 
* 0000..........:.....CALLSTCK:[0] 0x0900000004263D18 pdLog +  * 
* 0x88[1]                                                      * 
* 0x0900000004753A00@78@sqloDiagnoseFreeBlockFailure__FP8SMemFBl 
* + 0xE8[2]                                                    * 
* 0x090000000475384CsqloDiagnoseFreeBlockFailure__FP8SMemFBlk@gl 
* + 0x74[3] 0x09000000040295D4 sqlofmblkEx + 0x458[4]          * 
* 0x090000000471D28Csqlra_sqlW_mem_free_sibling_list__FP8sqlrr_c 
* 0x870[5]                                                     * 
* 0x09000000047261B0sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli 
* + 0x420[6]                                                   * 
* 0x0900000004725CC4sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli@ 
* + 0x74[7]                                                    * 
* 0x0900000005E31704sqlra_sqlW_check_for_cleanup__FP8sqlrr_cbUlP 
* + 0x60[8]                                                    * 
* 0x0900000004724614sqlra_sqlW_get_dynamic_section__FP8sqlrr_cbP 
* 0x09000000067C9E6Csqlra_load_var__FP8sqlrr_cbP16sqlra_cached_v 
* + 0x468                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB for Linux, Unix, Windows Version 9.7      * 
* FixPack 2                                                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 6 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 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
Problem was first fixed in Version 9.7 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.01.2010
31.05.2010
31.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.,
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList