suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT30759 Status: Closed

DB2 MAY RETURN SQL0901N ("COMBINED KEY LENGTH TOO BIG FOR SYSTEMTEMP")
WHEN EXECUTING QUERIES INVOLVING ZIGZAG JOINS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
SQL0901N with the message "Combined key length too big for
system temp" may be returned when executing queries involving
zigzag joins.

An example stack trace is seen below:

sqlzSetAndLog901 + 0x294
sqldCreateIndex__FP8sqeAgentP17SQLD_CREATEINX_CB + 0x6D4C
sqldIndexCreate__FP8sqeAgentP17SQLD_CREATEINX_CB + 0x2D88
sqlriCreateTempTableIndex__FP8sqlrr_cbP10sqlri_iudoUsT3 + 0x3EC
sqlrifiswp2__FP8sqlrr_cb + 0x480
sqldEvalDataPred__FP13SQLD_DFM_WORKPUlP10SQLD_DPRED + 0x3DC
sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL
Z_RIDPc@OL@24042 + 0x320
sqlsfetc__FP8sqeAgentP8SQLD_CCBiP10SQLD_DPREDPP10SQLD_VALUEP8SQL
Z_RIDPc + 0xA4
sqlriFetch__FP8sqlrr_cbP9sqlri_taol + 0x11C
sqlrita__FP8sqlrr_cb + 0x1D4
sqlriZigZagJoin__FP8sqlrr_cb + 0x23E4
sqlrihsjn__FP8sqlrr_cb + 0xAA0
sqlriunn__FP8sqlrr_cbP10sqlri_stob + 0x424
sqlriset__FP8sqlrr_cb + 0x1A8
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x90
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0x11C8
sqlrr_execimmd__FP14db2UCinterfaceP16db2UCprepareInfo + 0xF0
executeSection__10pvmPackageFP5sqlcaUib + 0x3BC4
executeSection__10pvmPackageFP5sqlcaUib + 0x12C
executeQuery__3PVMFUib + 0x100
run__3PVMFv + 0x124
pvm_entry + 0xD70
sqloInvokeFnArgs + 0x1A0
sqlriInvokeInvoker__FP10sqlri_ufobb + 0xCC
sqlriInvokeInvoker__FP10sqlri_ufobb + 0x1498
sqlricall__FP8sqlrr_cb + 0x1E0
sqlriSectInvoke__FP8sqlrr_cbP12sqlri_opparm + 0x90
sqlrr_process_execute_request__FP8sqlrr_cbib + 0xB5C
sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x1C4
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC
interface + 0x978
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x11E4
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x11E4
@72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0xDD8
@72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA8
@72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5FC
RunEDU__8sqeAgentFv + 0x40E1C
RunEDU__8sqeAgentFv + 0x124
EDUDriver__9sqzEDUObjFv + 0x130
sqloEDUEntry + 0x3A0
_pthread_body + 0xE8
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All A50 users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1 latest fixpack.                              *
****************************************************************
Local Fix:
Disable the use of zigzag join via setting the following
registry setting (it can be applied immediately) either through
db2set or via a guideline:
DB2_REDUCED_OPTIMIZATION="ZZJN OFF"
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* All A50 users                                                *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to 11.1 latest fixpack.                              *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.10.2019
10.03.2020
10.03.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)