DB2 - Problembeschreibung
Problem IT09584 | Status: Geschlossen |
DB2 MIGHT ABEND WHILE EXECUTING A QUERY WITH GROUP BY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
Under rare scenarios, DB2 might abend if the following conditions are true: 1) The query contains one or more GROUP BY clauses. 2) The number of grouping columns in the GROUP BY exceed the number of output columns. 3a) The subselect containing the GROUP BY is a parent to an existential subquery. OR 3b) The subselect containing the GROUP BY is joined with another subselect containing a DISTINCT clause. Here is an example of a stack you might see: sqloCrashOnCriticalMemoryValidationFailure + 0x34 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb + 0x2B8 diagnoseMemoryCorruptionAndCrash__13SQLO_MEM_POOLFUlCPCcCb@glue8 13 + 0x7C .MemTreePut.fdpr.clone.26__13SQLO_MEM_POOLFP8SMemNodeUlP17SqloCh unkSubgroup + 0x10 sqlofmblkEx + 0x288 add_keys__9sqlnq_qunFPiPP13sqlnq_deplistP17sqlnq_qclElemList + 0x120 sqlnr_addids__FP9sqlnq_qtbPiP17sqlnq_qclElemList + 0x1460 sqlnr_selbox_merge__FP9sqlnq_qtbP9sqlnq_qunT1Pii + 0x2D8 sqlnr_sel_mrg_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0x54 sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres s@AF484_228 + 0x17C sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 0xF4 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress + 0x84 sqlnr_any_mrg_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0x44 sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres s@AF484_228 + 0x17C sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 0xF4 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress + 0x84 sqlnr_perqun_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0x44 sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres s@AF484_228 + 0x17C sqlnr_priority__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 0xF4 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress + 0xAC sqlnr_allqun_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0xB0 sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres s@AF484_228 + 0x17C sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 0xF4 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress + 0x84 sqlnr_start_action__FP10sqlnr_qrwaPiP14sqlnr_progress + 0x100 sqlnr_comp__FPiiP16sqlnr_rule_stateP10sqlnr_qrwaP14sqlnr_progres s@AF484_228 + 0x17C sqlnr_seq__FPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass + 0xF4 sqlnr_rcc__FiP10sqlnr_qrwaPiP14sqlnr_progress + 0x84 sqlnr_exe__FP9sqlnq_qur + 0x38C sqlnr_exe__FP9sqlnq_qur@glue15FA + 0x98 sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq lrr_cmpl_enviT7PP9sqlnq_qur + 0x1E4 sqlnn_cmpl__FP8sqeAgentP11sqlrrstrings17sqlnn_compileModeT3P14sq lrr_cmpl_env + 0x40 sqlra_compile_var__FP8sqlrr_cbP14sqlra_cmpl_envPUciUsN54P14SQLP_ LOCK_INFOP16sqlra_cached_varPiPUl + 0x804 sqlra_find_var__FP8sqlrr_cbP17sqlra_cached_stmt13sqlra_stmt_idUi T4PUcT4UsUcP14sqlra_cmpl_env15sqlra_fill_modePiiT12_N313_T12_P14 SQLP_LOCK_INFOPP16sqlra_cached_varT12_PUlb + 0x5AC sqlra_get_var__FP8sqlrr_cbiT2bPbT5 + 0x7A8 sqlrr_prepare__FP14db2UCinterfaceP16db2UCprepareInfo + 0xC0 sqljs_ddm_prpsqlstt__FP14db2UCinterfaceP13sqljDDMObject + 0xC6C sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC interface + 0x184 .sqljsParse.fdpr.clone.45__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s qeAgentb + 0x3BC @63@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x2BC @63@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xA0 @63@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x27C sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 0xEC RunEDU__8sqeAgentFv + 0x2F0 EDUDriver__9sqzEDUObjFv + 0xE4 sqloEDUEntry + 0x250 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 fix pack 7. * **************************************************************** | |
Local-Fix: | |
Lösung | |
First fixed in DB2 10.5 fix pack 7. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.06.2015 20.01.2016 20.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |