DB2 - Problembeschreibung
Problem IT06948 | Status: Geschlossen |
QUERY WILL MULTIPLE SUBSUMABLE SCALAR SUBQUERIES MAY CAUSE DB2 TO ABEND | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Under rare conditions, DB2 might abend if the following conditions are satisfied 1) The query contains two or more scalar subqueries 2) Atleast 2 subqueries can be proven to be subsumed by each other and can only be executed once 3) Atleast one of these subqueries is used in a predicate 4) One or more of these subqueries are part of the output column list. Similar stack will be dumped in the trap file: sqlnr_matchmaker::nav_assign_max_levels sqlnr_matchmaker::nav_assign_max_levels sqlnr_matchmaker::nav_assign_max_levels sqlnr_matchmaker::nav_init sqlnr_matchmaker::form_matches sqlnr_form_common_subexprs sqlnr_optprep sqlnr_optprep_action sqlnr_comp sqlnr_seq sqlnr_rcc sqlnr_exe sqlnr_exe sqlnn_cmpl sqlnn_cmpl sqlra_compile_var sqlra_find_var sqlra_get_var sqlrr_prepare sqljs_ddm_prpsqlstt sqljsParseRdbAccessed .sqljsParse.fdpr.clone.45__FP13sqljsDrdaAsCbP14db2UCinterfaceP8s qeAgentb sqljsSqlam sqljsDriveRequests sqljsDrdaAsInnerDriver sqljsDrdaAsDriver sqeAgent::RunEDU sqzEDUObj::EDUDriver sqloEDUEntry | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Unknown * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 version 101 fix pack 5 * **************************************************************** | |
Local-Fix: | |
Manually rewrite the query to pushdown the subquery to the deepest subselect in the query. | |
Lösung | |
The fix is included in DB2 version 101 fix pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.02.2015 13.07.2015 13.07.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |