|
Problem IC66025
|
Status: Closed |
DOUBLE FREE MEMORY ISSUE IN THE SQLMON_STMT FUNCTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A double free memory issue can occur in the sqlmon_stmt
function.
This will cause a trap (SIGSEGV) with the following stack:
0x09000000085511F0 sqloCrashOnCriticalMemoryValidationFailure +
0x1C
0x0900000008556B88
sqloCrashOnCriticalMemoryValidationFailure@glue1E2 + 0x1C
0x090000000815F1CC sqlofmblkEx + 0x48
0x0900000009264360 __dt__11sqlmon_stmtFv + 0x244
0x09000000092B8214 __dt__11sqlmon_stmtFv@glue566 + 0x74
0x0900000008635094 cleanup_sqlmon_conn__11sqlmon_connFv + 0x7C
0x09000000091F2770 sqlm_a_exit__FP20sqle_agent_privatecb + 0x294
0x09000000091F924C
sqleTermDbConnect__FP13sqle_agent_cbP8sqledbcbP5sqlcaP21sqleTerm
ConnectStatus
+ 0x5CC
0x0900000009200B68 sqlesrsp__FP20sqle_agent_privatecbUcP5sqlcai
+ 0x594
The following message will be seen in the db2diag.log:
2009-03-26-00.27.05.524208-240 I10163963A1734 LEVEL: Severe
PID : 360488 TID : 1 PROC :
db2agent (SAMPLE) 0
INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE
APPHDL : 0-153
AUTHID : DB2INST1
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
0x07800000004810a0
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x0780000000481088 : FAB0 7800 0000 0470 0000 0000 0000 0000
..x....p........
0x0780000000481098 : 0780 0000 0048 1308
.....H..
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x07800000004810A0 : 0000 0000 0000 0240 0000 0000 0000 0009
.......@........
0x07800000004810B0 : 0000 0000 0000 0000 0000 0001 0000 0000
................
0x07800000004810C0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
CALLSTCK:
[0] 0x09000000085558C4
@49@sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0x944
[1] 0x0900000008554EB4
sqloDiagnoseFreeBlockFailure__FP8SMemFBlk@glue214 + 0x74
[2] 0x090000000815F3F0 sqlofmblkEx + 0x26C
[3] 0x0900000009264360 __dt__11sqlmon_stmtFv + 0x244
[4] 0x09000000092B8214 __dt__11sqlmon_stmtFv@glue566 + 0x74
[5] 0x0900000008635094 cleanup_sqlmon_conn__11sqlmon_connFv +
0x7C
[6] 0x09000000091F2770 sqlm_a_exit__FP20sqle_agent_privatecb +
0x294
This defect avoids the trap and will dump diagnostic
information. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who run queries *
****************************************************************
* PROBLEM DESCRIPTION: *
* A double free memory issue can occur in the sqlmon_stmt *
* *
* function. *
* *
* *
* *
* This will cause a trap (SIGSEGV) with the following stack: *
* *
* 0x09000000085511F0 *
* sqloCrashOnCriticalMemoryValidationFailure + *
* 0x1C *
* *
* 0x0900000008556B88 *
* *
* sqloCrashOnCriticalMemoryValidationFailure@glue1E2 + 0x1C *
* *
* 0x090000000815F1CC sqlofmblkEx + 0x48 *
* *
* 0x0900000009264360 __dt__11sqlmon_stmtFv + 0x244 *
* *
* 0x09000000092B8214 __dt__11sqlmon_stmtFv@glue566 + 0x74 *
* *
* 0x0900000008635094 cleanup_sqlmon_conn__11sqlmon_connFv + *
* 0x7C *
* 0x09000000091F2770 sqlm_a_exit__FP20sqle_agent_privatecb + *
* 0x294 *
* 0x09000000091F924C *
* *
* sqleTermDbConnect__FP13sqle_agent_cbP8sqledbcbP5sqlcaP21sqleTe
* ConnectStatus *
* *
* + 0x5CC *
* *
* 0x0900000009200B68 *
* sqlesrsp__FP20sqle_agent_privatecbUcP5sqlcai *
* + 0x594 *
* *
* *
* *
* The following message will be seen in the db2diag.log: *
* *
* 2009-03-26-00.27.05.524208-240 I10163963A1734 LEVEL: *
* Severe *
* PID : 360488 TID : 1 PROC : *
* db2agent (SAMPLE) 0 *
* *
* INSTANCE: DB2INST1 NODE : 000 DB : SAMPLE *
* APPHDL : 0-153 *
* *
* AUTHID : DB2INST1 *
* *
* 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 *
* *
* 0x07800000004810a0 *
* *
* DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes *
* *
* 0x0780000000481088 : FAB0 7800 0000 0470 0000 0000 0000 0000 *
* *
* ..x....p........ *
* *
* 0x0780000000481098 : 0780 0000 0048 1308 *
* *
* .....H.. *
* *
* DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes *
* *
* 0x07800000004810A0 : 0000 0000 0000 0240 0000 0000 0000 0009 *
* *
* .......@........ *
* *
* 0x07800000004810B0 : 0000 0000 0000 0000 0000 0001 0000 0000 *
* *
* ................ *
* *
* 0x07800000004810C0 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* *
* ................ *
* *
* CALLSTCK: *
* *
* [0] 0x09000000085558C4 *
* *
* @49@sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0x944 *
* *
* [1] 0x0900000008554EB4 *
* *
* sqloDiagnoseFreeBlockFailure__FP8SMemFBlk@glue214 + 0x74 *
* *
* [2] 0x090000000815F3F0 sqlofmblkEx + 0x26C *
* *
* [3] 0x0900000009264360 __dt__11sqlmon_stmtFv + 0x244 *
* *
* [4] 0x09000000092B8214 __dt__11sqlmon_stmtFv@glue566 + *
* 0x74 *
* [5] 0x0900000008635094 *
* cleanup_sqlmon_conn__11sqlmon_connFv + *
* 0x7C *
* *
* [6] 0x09000000091F2770 *
* sqlm_a_exit__FP20sqle_agent_privatecb + *
* 0x294 *
* *
* *
* *
* This defect avoids the trap and will dump diagnostic *
* *
* information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.7 FP2 or newer. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 |
Upgrade to DB2 v9.7 FP2 or newer. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.02.2010
25.05.2010
08.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
