DB2 CONNECT / DB2CONNCT / A10 - DB2

If you have a CLI application, you may see an error related to a 
possible memory corruption due to a double free in your 
db2diag.log during the disconnect. 
 
The message should look like the following : 
 
  2014-01-17-15.41.23.130000+120 I612956H924        LEVEL: 
Severe 
  PID     : 2844                 TID  : 1280        PROC : 
dllhost.exe 
  INSTANCE: DB2                  NODE : 000 
 
  EDUID   : 1280 
 
  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, 4 
bytes 
  0x0637d540 
 
  DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
 
  0x0637D528 : 7063 B0FA 0000 0000 0000 0000 2000 0000 
pc.......... ... 
  0x0637D538 : 7063 B0FA 064C 454E 
pc...LEN 
  DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
 
  0x0637D540 : 0800 0000 0000 0000 E8AF 2CDB 0801 0000 
..........,..... 
  0x0637D550 : 3548 B14A 5809 6400 7063 B0FA 533B 5155 
5H.JX.d.pc..S;QU 
  0x0637D560 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
 
 
  2014-01-17-15.41.23.130000+120 I613882H318        LEVEL: 
Severe 
  PID     : 2844                 TID  : 1280        PROC : 
dllhost.exe 
  INSTANCE: DB2                  NODE : 000 
 
  EDUID   : 1280 
 
  FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, 
  probe:30 
 
  DATA #1 : String, 12 bytes 
 
  Double free.

**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI applications                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP5 or later                             * 
****************************************************************

The problem was first fixed in DB2 10.1 FP5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.11.2014
13.07.2015
13.07.2015