DB2 - Problem description
| Problem IC79269 | Status: Closed |
DB2 ENCOUNTERS MEMORY CORRUPTION DURING COMPILATION OF A VERY LENGTHY SQL STATEMENT | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problem description: | |
DB2 encounter memory corruption during compilation of a very
lengthy SQL statement and the optimized SQL starts with a
non-alphabet char, e.g.
Optimized Statement:
-------------------
$WITH
CONTEXT$($CONSTRAINT$(CCDB.DENTAL_CLAIM_DTL_1.FK_DENTAL_CLAIM_DT
L))
INSERT INTO CCDB.DENTAL_CLAIM_DTL_1 AS Q3
................
DB2 can encounter this memory corruption at various places, one
example is it encounters memory corruption in
sqlngStorePlanInfo() with the following message in db2diag.log:
2011-10-04-01.22.20.695815-300 I191913306E1987 LEVEL: Severe
PID : 31384 TID : 46923947960640PROC :
db2sysc 0
INSTANCE: bculinp NODE : 000 DB :
PCFTEST
APPHDL : 0-6080 APPID:
10.30.5.32.35928.111004061410
AUTHID : STGUSR
EDUID : 66551 EDUNAME: db2agent (PCFTEST) 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
0x00002aad360480e0
DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
0x00002AAD360480C8 : E4AF 2CDB 080F 2000 86AC 16E5 A721 1607
..,.........!..
0x00002AAD360480D8 : 3960 D3AA 0200 B02E
9`......
DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
0x00002AAD360480E0 : 2E2E 2B30 3030 3132 3039 3035 3838 2E2C
..+00012090588.,
0x00002AAD360480F0 : 202B 3030 3031 3230 3930 3538 382E 2C20
+00012090588.,
0x00002AAD36048100 : 2B30 3030 3132 3039 3035 3838 2E2C 202B
+00012090588., +
CALLSTCK:
[0] 0x00002AAAABB077B8 pdLog + 0x398
[1] 0x00002AAAAD4B8018
/db2home/bculinp/sqllib/lib64/libdb2e.so.1 + 0x27D7018
[2] 0x00002AAAAE19F426 sqlofmblkEx + 0x8F0
[3] 0x00002AAAABAD41CC _Z9sqlofmblkPv + 0x6
[4] 0x00002AAAABDAF48F _Z18sqlngStorePlanInfoP9sqlng_blk +
0x4E2F
[5] 0x00002AAAABD8BAED _Z10sqlng_mainP9sqlnq_qur + 0xFC1
[6] 0x00002AAAABDB6C10
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq
lrr_cmpl_enviiPP9sqlnq_qur
+ 0x309E
[7] 0x00002AAAABDB3B6D
_Z10sqlnn_cmplP8sqeAgentP11sqlrrstrings17sqlnn_compileModesP14sq
lrr_cmpl_env
+ 0x21
[8] 0x00002AAAAC0E098C
_Z17sqlra_compile_varP8sqlrr_cbP14sqlra_cmpl_envPhitiiiiiP14SQLP
_LOCK_INFOP16sqlra_cached_varPiPm
+ 0x6A8
[9] 0x00002AAAAC0EBDB6
_Z14sqlra_find_varP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idj
jPhjthP14sqlra_cmpl_env15sqlra_fill_modePiiS8_iiiS8_P14SQLP_LOC
+ 0x538 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW Version 9.7 Fix Pack 6 * **************************************************************** | |
| Local Fix: | |
Simplify the SQL statement may avoid the symptom. | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
Problem was first fixed in Version 9.7 Fix Pack 6 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.10.2011 11.06.2012 11.06.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|