|
Problem IC62719
|
Status: Closed |
POSSIBLE MEMORY CORRUPTION DETECTED MESSAGE REPORTED IN FREEBLOCK - SQLDMCLO() |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A "possible memory corruption detected" message reported while
attempting to free a memory block. The issue is that we
attempt to free a memory block twice.
This problem is specific to three things:
- Cursors using currently committed.
- Concentrator environment.
- Cursors declared WITH HOLD.
2009-07-07-11.36.56.176620-240 I1370130A1807 LEVEL:
Severe PID : 1318930 TID : 13879 KTID :
4063443PROC : db2sysc 0
INSTANCE: minger5 NODE : 000 DB :
MYDB APPHDL : 0-191 APPID:
9.23.1.74.42256.090707153553
AUTHID : MINGER5
EDUID : 13879 EDUNAME: db2agent (MYDB) 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
0x000000012229df40
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x000000012229DF28 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x000000012229DF38 : 0000 0000 0000 0000
........
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x000000012229DF40 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x000000012229DF50 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x000000012229DF60 : 0000 0000 0000 0000 0000 0000 0000 0000
................
CALLSTCK:
[0] 0x0900000003D48DF0
sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0x130
[1] 0x0900000003D4AB2C sqlofmblkEx + 0x1CC
[2] 0x0900000004312774 sqlofmblk__FPv + 0x14
[3] 0x090000000431862C sqldmclo__FP8sqeAgentPP8SQLD_CCBi +
0x110C
[4] 0x09000000058DA824 sqlriclo__FP8sqlrr_cbP9sqlri_taoi +
0x244
[5] 0x09000000047D33B0
sqlricjp__FP8sqlrr_cbP12sqlri_opparmilT4 + 0x450
[6] 0x09000000047E0B4C sqlricls_simple__FP8sqlrr_cbil + 0x7AC
[7] 0x09000000058C6990 sqlricls__FP8sqlrr_cbiN32 + 0x270
[8] 0x09000000058C6D08
sqlra_close_section__FP8sqlrr_cbP25sqlra_sql_context_siblingiN63
+ 0x268
[9] 0x09000000058C7650
sqlrr_process_close_request__FP8sqlrr_cbiN32 + 0x2B0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* The issue here is that we try to free a memory block twice *
* The memory block is from private memory. *
* We free a threads private memory when it exits; this is how *
* we *
* free the memory block in this instance. However, an open *
* cursor *
* can still reference the memory block and will attempt a *
* second free *
* when the cursor is closed. *
* *
* This problem is specific to three things: *
* - Cursors using currently committed. *
* - Concentrator environment. *
* - Cursors declared WITH HOLD. *
* *
* 2009-07-07-11.36.56.176620-240 I1370130A1807 LEVEL: *
* Severe *
* PID : 1318930 TID : 13879 KTID : *
* 4063443 *
* PROC : db2sysc 0 *
* INSTANCE: minger5 NODE : 000 DB : *
* MYDB *
* APPHDL : 0-191 APPID: *
* 9.23.1.74.42256.090707153553 *
* AUTHID : MINGER5 *
* EDUID : 13879 EDUNAME: db2agent (MYDB) 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 *
* 0x000000012229df40 *
* DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes *
* 0x000000012229DF28 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x000000012229DF38 : 0000 0000 0000 0000 *
* ........ *
* DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes *
* 0x000000012229DF40 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x000000012229DF50 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x000000012229DF60 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* CALLSTCK: *
* [0] 0x0900000003D48DF0 *
* sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0x130 *
* [1] 0x0900000003D4AB2C sqlofmblkEx + 0x1CC *
* [2] 0x0900000004312774 sqlofmblk__FPv + 0x14 *
* [3] 0x090000000431862C sqldmclo__FP8sqeAgentPP8SQLD_CCBi + *
* 0x110C *
* [4] 0x09000000058DA824 sqlriclo__FP8sqlrr_cbP9sqlri_taoi + *
* 0x244 *
* [5] 0x09000000047D33B0 *
* sqlricjp__FP8sqlrr_cbP12sqlri_opparmilT4 + 0x450 *
* [6] 0x09000000047E0B4C sqlricls_simple__FP8sqlrr_cbil + *
* 0x7AC *
* [7] 0x09000000058C6990 sqlricls__FP8sqlrr_cbiN32 + 0x270 *
* [8] 0x09000000058C6D08 *
* sqlra_close_section__FP8sqlrr_cbP25sqlra_sql_context_siblingiN
* + 0x268 *
* [9] 0x09000000058C7650 *
* sqlrr_process_close_request__FP8sqlrr_cbiN32 + 0x2B0 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 9.7 FP1 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
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 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
|
| Solution |
First fixed in DB2 UDB Version 9.7 FixPak 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.08.2009
17.02.2010
17.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
