|
Problem IC63054
|
Status: Closed |
In a mixed XA/non-XA env,a transactional request may panic when DDL requests/failed XA requests were executed inside XA env. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
There is a DB2 logic issue which caused a double free pointer
action when transactional request is issued. This will happen if
there is DDL requests were executed and a failed XA requests
were issued inside XA environment.
The entries in the db2diag.log should look like this:
2009-08-28-05.53.56.783147-420 I56829172A1910 LEVEL: Severe
PID : 28080 TID : 1 PROC :
db2agent (VBUILDDB) 0
INSTANCE: db2vbprd NODE : 000 DB :
VBUILDDB
APPHDL : 0-814 APPID: /1149826.4195.00060013001A
AUTHID : V859640
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
0x0000000319718920
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x0000000319718908 : FAB0 0000 0031 9710 3E69 CAD5 00EB 78DB
.....1..>i....x.
0x0000000319718918 : FAB0 0000 0031 9710
.....1..
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x0000000319718920 : 0000 0000 0000 0000 0000 0000 0000 0005
................
0x0000000319718930 : 000A 0008 5052 4956 5F55 5345 5253 0000
....PRIV_USERS..
0x0000000319718940 : 0000 0000 0000 0000 0000 0000 0000 0000
................
CALLSTCK:
[0] 0xFFFFFFFF7BFB409C
__1cbJsqloMemSearchForChunkSubgroupHeader6FkLkb_pnRSqloChunkSubg
roup__ + 0x1C4
[1] 0xFFFFFFFF7BFB4D74 sqlofmblkEx + 0x664
[2] 0xFFFFFFFF7CD2BA40
__1cYsqlrr_end_tran_after_DPS6FpnIsqlrr_cb_ii_i_ + 0x4E0
[3] 0xFFFFFFFF7CD2C6AC
__1cMsqlrrcom_dps6FpnIsqlrr_cb_iipnNsqlxaCallInfo__i_ + 0x714
[4] 0xFFFFFFFF7CD2D0D4 __1cIsqlrrcom6FpnIsqlrr_cb_ii_i_ +
0x46C
[5] 0xFFFFFFFF7CD0F5E0
__1cMsqlrr_commit6FpnOdb2UCinterface__i_ + 0xC0
[6] 0xFFFFFFFF7BF42674
__1cSsqljsSyncCommitted6FpnOdb2UCinterface__i_ + 0x354
[7] 0xFFFFFFFF7BF3F75C
__1cRsqljs_ddm_syncctl6FpnOdb2UCinterface_pnOsqljsDDMObject__i_
+ 0x2A4
[8] 0xFFFFFFFF7BF26084
__1cVsqljsParseRdbAccessed6FpnNsqljsDrdaAsCb_pnOsqljsDDMObject_p
nOdb2UCinterface__i_ + 0x2E4
[9] 0xFFFFFFFF7BF26E00
__1cKsqljsParse6FpnNsqljsDrdaAsCb_pnOdb2UCinterface__i_ + 0x488 |
| Problem Summary: |
There is a DB2 logic issue which caused a double free pointer
action when transactional request is issued. This will happen if
there is DDL requests were executed and a failed XA requests
were issued inside XA environment.
The entries in the db2diag.log should look like this:
2009-08-28-05.53.56.783147-420 I56829172A1910 LEVEL: Severe
PID : 28080 TID : 1 PROC :
db2agent (VBUILDDB) 0
INSTANCE: db2vbprd NODE : 000 DB :
VBUILDDB
APPHDL : 0-814 APPID: /1149826.4195.00060013001A
AUTHID : V859640
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
0x0000000319718920
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x0000000319718908 : FAB0 0000 0031 9710 3E69 CAD5 00EB 78DB
.....1..>i....x.
0x0000000319718918 : FAB0 0000 0031 9710
.....1..
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x0000000319718920 : 0000 0000 0000 0000 0000 0000 0000 0005
................
0x0000000319718930 : 000A 0008 5052 4956 5F55 5345 5253 0000
....PRIV_USERS..
0x0000000319718940 : 0000 0000 0000 0000 0000 0000 0000 0000
................
CALLSTCK:
[0] 0xFFFFFFFF7BFB409C
__1cbJsqloMemSearchForChunkSubgroupHeader6FkLkb_pnRSqloChunkSubg
roup__ + 0x1C4
[1] 0xFFFFFFFF7BFB4D74 sqlofmblkEx + 0x664
[2] 0xFFFFFFFF7CD2BA40
__1cYsqlrr_end_tran_after_DPS6FpnIsqlrr_cb_ii_i_ + 0x4E0
[3] 0xFFFFFFFF7CD2C6AC
__1cMsqlrrcom_dps6FpnIsqlrr_cb_iipnNsqlxaCallInfo__i_ + 0x714
[4] 0xFFFFFFFF7CD2D0D4 __1cIsqlrrcom6FpnIsqlrr_cb_ii_i_ +
0x46C
[5] 0xFFFFFFFF7CD0F5E0
__1cMsqlrr_commit6FpnOdb2UCinterface__i_ + 0xC0
[6] 0xFFFFFFFF7BF42674
__1cSsqljsSyncCommitted6FpnOdb2UCinterface__i_ + 0x354
[7] 0xFFFFFFFF7BF3F75C
__1cRsqljs_ddm_syncctl6FpnOdb2UCinterface_pnOsqljsDDMObject__i
+ 0x2A4
[8] 0xFFFFFFFF7BF26084
__1cVsqljsParseRdbAccessed6FpnNsqljsDrdaAsCb_pnOsqljsDDMObject_p
nOdb2UCinterface__i_ + 0x2E4
[9] 0xFFFFFFFF7BF26E00
__1cKsqljsParse6FpnNsqljsDrdaAsCb_pnOdb2UCinterface__i_ + 0x488 |
| Local Fix: |
Either taking out the DDL operation out of XA environment or not
issue failed XA requests. |
| 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 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 2. |
| Workaround |
Either take out the DDL operation out of XA environment or not
issue failed XA requests. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.09.2009
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
