|
Problem IC77559
|
Status: Closed |
INSERT OR UPDATE WITH INDEX COMPRESSION MAY CAUSE MEMORY CORRUPTION AND CRASH |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
If the indexes for a table are compressed then any of the
following operations can cause a crash :
- INSERT
- UPDATE
- IMPORT
- LOAD
- CREATE INDEX
- REORG INDEXES
The following are example stacktraces for the crash:
<StackTrace>
-------Frame------ ------Function + Offset------
sqloCrashOnCriticalMemoryValidationFailure + 0x20
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc + 0x27C
diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCc@glue7C4
+x78
MemTreeGet__13SQLO_MEM_POOLFCUlT1PPvPP17SqloChunkSubgroupPP12SMe
mLostNode + 0x54
.allocateMemoryBlock.fdpr.clone.26__13SQLO_MEM_POOLFCUlUlT1UiT1
PPvPP17SqloChunk
SubgroupPP12SMemLostNodeCP12SMemLogEvent + 0x80
sqlogmblkEx + 0x72C
sqldAllocWorkArea__FP8sqeAgentP16SQLD_WORK_MEMORYUiiN23PPc +
0x98
sqldAllocWorkArea__FP8sqeAgentP16SQLD_WORK_MEMORYUiiN23PPc@glue5
68 + 0x8C
sqldGetWorkArea__FP8sqeAgentiPPcUiT2@glueC2A + 0x2C
@147@sqlipcLogPrefixImprovement__FP7SQLI_CBP14SQLI_PAGE_DESCT2lP
9SQLI_SLOT + 0x1FC
@147@sqlipcCopyTempPgToCurrentPg__FP7SQLI_CBP14SQLI_PAGE_DESCP9S
QLI_SLOTT2lP6ACT_PG + 0x270
@147@sqlipcPhysicalMerge__FP7SQLI_CBP6ACT_PGP14SQLI_PAGE_DESCP27
SQLI_PREFIX_META
_DATA_TABLEUlN25lP9SQLI_SLOT + 0x688
sqlipcOptimizePrefixes__FP7SQLI_CBP6ACT_PGP14SQLI_PAGE_DESCP9SQL
I_SLOTUlT5PUl + 0x62C
sqlipcOptimizePrefixes__FP7SQLI_CBP6ACT_PGP14SQLI_PAGE_DESCP9SQL
I_SLOTUlT5PUl@glue1500 + 0x74
@147@addkeyToLeaf__FP7SQLI_CBP11SQLI_SAGLOBP9SQLI_SLOT + 0x814
</StackTrace>
<StackTrace>
-------Frame------ ------Function + Offset------
?unknown + 0x0
memcpy__FPvPCvUl + 0x2C
sqlo_md_mcpy + 0x208
sqlipcUseLongerPrefix__FP7SQLI_CBPcN32PUs + 0xFB4
sqlipcPutNewSuffixOnTempPg__FP7SQLI_CBP14SQLI_PAGE_DESCT2lN24P21
SQLI_PREFIX_META_DATA + 0x4F0
sqlipcCopyModifiedSuffixesWithRelocate__FP7SQLI_CBP14SQLI_PAGE_D
ESCT2P9SQLI_SLOTUl + 0x520
sqlipcPhysicalMerge__FP7SQLI_CBP6ACT_PGP14SQLI_PAGE_DESCP27SQLI_
PREFIX_META_DATA_TABLEUlN25lP9SQLI_SLOT + 0x4D0
sqlipcOptimizePrefixes__FP7SQLI_CBP6ACT_PGP14SQLI_PAGE_DESCP9SQL
I_SLOTUlT5PUl + 0x4A0
sqliNormalAddKey__FP7SQLI_CBP14SQLI_PAGE_DESCP9SQLI_SLOTP8SQLD_K
EYP12SQLI_KEYDATA + 0x4AC
sqliakn__FP7SQLI_CBP14SQLI_PAGE_DESCP9SQLI_SLOTP8SQLD_KEYP12SQLI
_KEYDATAPUc + 0x668
addkeyToLeaf__FP7SQLI_CBP11SQLI_SAGLOBP9SQLI_SLOT + 0x2C8
procLeaf2Add__FP7SQLI_CBP11SQLI_SAGLOBP9SQLI_SLOTiP12SQLI_KEYDAT
A + 0x4D4
sqlischa__FP7SQLI_CBP11SQLI_SAGLOBiUi + 0xFC4
next_level__FP7SQLI_CBP11SQLI_SAGLOBiUi + 0x138
sqlischa__FP7SQLI_CBP11SQLI_SAGLOBiUi + 0xF4C
sqliaddk__FP8sqeAgentP9SQLD_IXCBP8SQLD_KEYP12SQLI_KEYDATAP14SQLP
_LOCK_INFOP8SQLP
_LRBUlP10SQLI_IXPCR + 0xF88
sqldKeyInsert__FP13SQLD_DFM_WORKP16SQLD_TABLE_CACHET2P13SQLD_TDA
TARECiUl + 0x7B4
sqldRowInsert__FP8sqeAgentUsT2UcUliPP10SQLD_VALUEP13SQLD_TDATARE
CP8SQLZ_RID + 0x1230
sqlrinsr__FP8sqlrr_cbUsT2iT2PP10SQLD_VALUEUlP8SQLZ_RID + 0xE8
sqlriisr__FP8sqlrr_cb + 0x4F0
sqlriExecThread__FP8sqlrr_cbP12sqlri_opparm + 0x584
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x4DC
sqlrr_process_execute_request__FP8sqlrr_cbi + 0x1880
sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x5A4
sqljs_ddm_excsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0x5D8
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x1E0
sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb + 0x21
C
sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x4AC
sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x15C
sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x478
sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0x23C
RunEDU__8sqeAgentFv + 0x3AC
EDUDriver__9sqzEDUObjFv + 0x19C
sqlzRunEDU__FPcUi + 0x3C
sqloEDUEntry + 0x6A4
</StackTrace> |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description above *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.8 FP4 *
**************************************************************** |
| Local Fix: |
db2set DB2_INDEX_COMPRESSION=OFF
followed by db2stop/db2start to pick up this change,
then drop and recreate the indexes.
Alternatively use the ALTER INDEX command with the COMPRESS NO,
following by using the REORG INDEXES command to recreate the
problem index as uncompressed |
| available fix packs: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Problem first fixed in DB2 V9.8 FP4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.07.2011
10.08.2011
10.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
