DB2 - Problem description
Problem IC66848 | Status: Closed |
TRAP IN SQLICOMPAREKEYS WHEN A SHARED BLOCK INDEX SCAN INVOLVES A NULL START/STOP KEY ON A NON-NULLABLE COLUMN | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The problem happens when you have the following: - an MDC table with an organize by clause on a column that is not nullable - block index scans that are eligible for scan sharing running on the block index for the not nullable column - a new block index scan on that same block index and this one has a start key or stop key of NULL (most often from an outer join) Example stack: <StackTrace> -----FRAME------ ------FUNCTION + OFFSET------ FFFFFD7FF76F09B8 _memcpy + 0x0988 (/lib/amd64/libc.so.1) FFFFFD7FFC23CD27 __1cPsqliCompareKeys6FpnHSQdDLI_CB_pnISQdDLD_KEY_3pv_i_ + 0x004 7 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FF9A6C97C __1cXsqldSGMGetStartLocation6FpnNSQdDLD_DFM_WORK_pnISQdDLD_TCB_ pnJSQdDLD_IXCB_pnYSQdDLD_SGM_SHARINGSET_NODE_pnISQdDLD_KEY_nISQd DLZ_RID_i9AiLflp 9Ap9BppnVSQdDLD_SGM_SCANNER_NODE__l_ + 0x0bcc (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FF9A65835 __1cYsqldInsertScannerIntoSGM6FpnNSQdDLD_DFM_WORK_pnISQdDLD_TCB _pnJSQdDLD_IXCB_pnKSQdDLI_IXPCR_LLLilIipipl_i_ + 0x05b5 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FF98B3330 __1cZsqldSetupSharingScanInSGM6FpnIsqeAgent_pnISQdDLD_CCB_pnNSQ dDLD_DFM_WORK_pnLSQdDLD_IXINFO_pnKSQdDLI_IXPCR_pnJSQdDLD_IXCB_HL CiIfi_i_ + 0x067 0 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FF9971AB1 __1cVsqldSetupCCBDPartInfo6FpknOSQdDLD_SCANINFO2_pnISQdDLD_CCB_ pnQSQdDLD_CLOSEDSCANS_pnJSQdDLD_IXCB_pnSSQdDLD_CCB_DPARTINFO__i_ + 0x2cf1 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FF99738B0 __1cMsqldScanOpen6FpnIsqeAgent_pnOSQdDLD_SCANINFO1_pnOSQdDLD_SC ANINFO2_ppv_i_ + 0x16e0 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FFB6656E2 __1cIsqlriopn6FpnIsqlrr_cb_pnJsqlri_tao_pi_i_ + 0x0bd2 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FFB7758B6 __1cRsqlritaSimplePerm6FpnIsqlrr_cb__i_ + 0x0256 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FFB6D0448 __1cPsqlriSectInvoke6FpnIsqlrr_cb_pnMsqlri_opparm__i_ + 0x0448 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FFB32DA89 __1cbBsqlrr_process_fetch_request6FpnOdb2UCinterface__i_ + 0x08 c9 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FFB324F45 __1cKsqlrr_open6FpnOdb2UCinterface_pnPdb2UCCursorInfo__i_ + 0x0 bd5 (/export/db2/install/V9.7/lib64/libdb2e.so.1) FFFFFD7FF9E6B4C2 __1cQsqljs_ddm_opnqry6FpnOdb2UCinterface_pnNsqljDDMObject__i_ + 0x0312 (/export/db2/install/V9.7/lib64/libdb2e.so.1) | |
Problem Summary: | |
Users Affected: Users with an MDC table organized by a nont null column Peoblem description: DB2 can trap in sqliCompareKeys during a shared index scan. Problem Summary: See above | |
Local Fix: | |
Disable scan sharing for that table via an optimizer guideline | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fixpak 2. | |
Workaround | |
Disable scan sharing for that table via an optimizer guideline | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67149 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.03.2010 01.07.2010 03.02.2014 |
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 |