|
Problem IC72604
|
Status: Geschlossen |
DB2 may abend when query has an OR predicate whose subterm predicates share common table(s) with join predicate(s) |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
DB2 database may abend if the following conditions are
satisfied:
1. One query SELECT WHERE clause has join predicates
(call jnPrds) as well as an OR predicate (called orPrd).
2. jnPrds involved a set of table, called JnPrdables.
3. orPrd is composed of two or more subterm predicates
(orPrd1 OR orPrd2 OR .. OR orPrdN). Divide these subterm
predicates into two groups:
lOrPrd = (orPrd1 OR orPrd2 OR .. OR orPrdN-1) and
rOrPrd = orPrdN. Now we know orPrd = (lOrPrd OR rOrPrd).
4. Call lOrPrd referenced table set as lOrPrdTables and rOrPrd
referenced table set as rOrPrdTables.
5. lOrPrdTables and rOrPrdTables have exactly one intersect
table.
6. One table from JnPrdables is contained in either
lOrPrdTables or rOrPrdTables but not both of them.
The trap file may contain various stack trace(s), e.g.:
1. Stack Trace:
...
sqlnq_qunqncchild::pp
sqlnq_qnc::local
sqlnr_test_selectBT
sqlnr_collapse_union_distinct_of_same_table
sqlnr_qrwprep_phase1
sqlnr_prep1_action
sqlnr_comp
sqlnr_seq
sqlnr_rcc
sqlnr_exe
sqlnn_cmpl
sqlnn_cmpl
sqlra_compile_var
sqlra_find_var
sqlra_get_var
sqlrr_prepare
sqljs_ddm_prpsqlstt
sqljsParseRdbAccessed
...
2. Stack Trace:
...
sqlnr_matchmaker::nav_assign_max_levels
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_comp
sqlnr_seq
sqlnr_rcc
sqlnr_exe
... |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 4. *
**************************************************************** |
| Local-Fix: |
db2set DB2COMPOPT=0,32768
Please recycle the instance after setting the above registry
variable. |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 Version 9.7 Fix Pack 4. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 16.11.2010
01.05.2011
01.05.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP4
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.4
|
 |
| 9.7.0.5
|
|
