|
Problem IC87850
|
Status: Closed |
DB2 CAN TRAP IN SQLODIAGNOSEFREEBLOCKFAILURE WHEN USING 2 PHASE COMMIT. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
db2 can trap in SQLODIAGNOSEFREEBLOCKFAILURE when using 2 phase
commit.
You can find the following entry in db2diag.log.
2009-11-03-18.28.55.241653-300 I29082A1746 LEVEL: Severe
PID : 1237220 TID : 6942 PROC : db2sysc
INSTANCE: svtdbm10 NODE : 000 DB : SDBS
APPHDL : 0-118 APPID:
*LOCAL.svtdbm10.091103215453
AUTHID : SVTDBM10
EDUID : 6942 EDUNAME: db2agent (SDBS)
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
0x0780000000d53cc0
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x0780000000D53CA8 : FAB0 7800 0000 0D50 0780 0000 00D5 31C8
..x....P......1.
0x0780000000D53CB8 : 0780 0000 00D5 5568
......Uh
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x0780000000D53CC0 : 0000 0000 0000 0360 0000 0000 0000 0009
.......`........
0x0780000000D53CD0 : 0000 0000 0000 0000 0000 0001 0000 0000
................
0x0780000000D53CE0 : 0000 0000 0000 0000 0000 0000 0000 0000
................
CALLSTCK:
[0] 0x090000001203CEE8
sqloDiagnoseFreeBlockFailure__FP8SMemFBlk + 0xE8
[1] 0x090000001203CD40 sqlofmblkEx + 0x780
[2] 0x0900000012773514 __dl__10sqm_objectFPv + 0x14
[3] 0x090000001229B8A0 __dt__11sqlmon_stmtFv + 0x380
[4] 0x0900000012292E68 cleanup_sqlmon_conn__11sqlmon_connFv +
0x448
[5] 0x0900000014E02CFC sqlm_a_exit__FP8sqeAgent + 0x5BC
[6] 0x09000000126AE96C
AppStopUsing__14sqeApplicationFP8sqeAgentUcP5sqlca + 0x136C
[7] 0x0900000012069EBC sqlesrspWrp__FP14db2UCinterface + 0x9C
[8] 0x0900000012067508 sqleUCagentConnectReset + 0xE8
[9] 0x09000000132383D0
sqljsCleanup__FP8sqeAgentP14db2UCconHandle + 0x1F0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Recommended to upgrade to DB2 for LUW version 10.1 fixpack 2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Fix available from DB2 for LUW version 10.1 fixpack 2 onwards. |
| Workaround |
Keep the statement monitor switch OFF at the database manager
level as well as the local application level. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.11.2012
01.01.2013
01.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
