DB2 FOR LUW / DB2FORLUW / A10 - DB2

DB2 instance may crash with a message indicating that we are 
attempting to free memory that was already freed. This situation 
can occur after several attempts are made to restart the vendor 
library. The following symptoms can be found in db2diag.log: 
 
 
1) more than one attempt to restart vendor library similar to 
 
   2014-03-14-05.08.06.035578-240 I691010A392        LEVEL: 
Warning 
   PID     : 10158162             TID  : 12610       PROC : 
db2sysc 0 
   INSTANCE: db2inst1             NODE : 000 
   EDUID   : 12610                EDUNAME: db2logmgr (SAMPLE) 0 
   FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogFile, probe:3800 
   MESSAGE : Retrying log retrieve.  Restarting vendor and then 
calling retrieve. 
 
 
2) one last error from vendor library followed by detection of 
memory corruption and "double free" message: 
 
   2014-03-14-05.08.06.240791-240 I701583A438        LEVEL: 
Error 
   PID     : 10158162             TID  : 12610       PROC : 
db2sysc 0 
   INSTANCE: db2inst1             NODE : 000 
   EDUID   : 12610                EDUNAME: db2logmgr (SAMPLE) 0 
   FUNCTION: DB2 UDB, data protection services, 
sqlpgRetrieveLogVendor, probe:3600 
   RETCODE : 
ZRC=0x86100024=-2045771740=SQLP_SHRLIB_VENDOR_DEV_ERR 
             "A vendor device reported a shared library error." 
 
   2014-03-14-05.08.06.240947-240 I702022A1616       LEVEL: 
Severe 
   PID     : 10158162             TID  : 12610       PROC : 
db2sysc 0 
   INSTANCE: db2inst1             NODE : 000 
   EDUID   : 12610                EDUNAME: db2logmgr (SAMPLE) 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 
   0x0700000082e0ffc0 
   DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes 
   0x0700000082E0FFA8 : FAB0 7000 0008 2E00 0000 0000 0000 0000 
..p............. 
   0x0700000082E0FFB8 : 0000 0000 0000 0000 
........ 
   DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes 
   0x0700000082E0FFC0 : 0000 0000 0000 0040 0000 0000 0000 0000 
.......@........ 
   0x0700000082E0FFD0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
   0x0700000082E0FFE0 : 0000 0000 0000 0000 0000 0000 0000 0000 
................ 
   CALLSTCK: 
     [0] 0x09000000053E8F90 pdLog + 0x80 
     [1] 0x0900000005A8CBA4 
@78@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0xF4 
     [2] 0x0900000005A8C9E0 
sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb@glue6D5 + 0x78 
     [3] 0x090000000573B7C4 sqlofmblkEx + 0x80 
     [4] 0x09000000054F6044 
sqlpTermVendorAPI__FPP15SQLPG_VENDOR_CB + 0x78 
     [5] 0x090000000799F87C sqlpgRetrieveLogFile__FP9SQLP_DBCB + 
0x130C 
     [6] 0x0900000007999E24 
sqlpgHandleLogMgrPost__FP9SQLP_DBCBUi + 0xE54 
     [7] 0x090000000799804C sqlpgLogManager__FPcUi + 0xCA8 
     [8] 0x09000000056E2A4C sqloEDUEntry + 0x49C 
     [9] 0x09000000004FDD30 _pthread_body + 0xF0 
 
   2014-03-14-05.08.06.241223-240 I703639A355        LEVEL: 
Severe 
   PID     : 10158162             TID  : 12610       PROC : 
db2sysc 0 
   INSTANCE: db2inst1             NODE : 000 
   EDUID   : 12610                EDUNAME: db2logmgr (SAMPLE) 0 
   FUNCTION: DB2 UDB, SQO Memory Management, 
sqloDiagnoseFreeBlockFailure, probe:30 
   DATA #1 : String, 12 bytes 
   Double free.

**************************************************************** 
* USERS AFFECTED:                                              * 
* all using backup to vendor library                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 Fix Pack 6                           * 
****************************************************************

first fixed in version 10.1 Fix Pack 6

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

19.03.2014
04.02.2016
04.02.2016