|
Problem IC61599
|
Status: Closed |
ENHANCE FACTORIZATION OF A COMPLEX TYPE OF OR PREDICATE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
This fix improves the predicate factorization of OR predicate
whose all subterms have exactly matched clause. Given an example
predicate
(((col1 = 1 and col2 = 2) or col1 >= 100) and col3 = 3) or
(((col1 = 1 and col2 = 2) or col1 >= 100) and col4 = 4)
, this fix will rewrite the predicate to
((col1 = 1 and col2 = 2) or col1 >= 100) and (col3 = 3 or col4 =
4).
Here, the exactly matched clause is mixed with OR and AND. The
comparison can be any type including >=, >, =, <, <=, IS NULL,
IS NOT NULL, IN, etc. Both comparison operands can be literal
including special register and host variable, single base table
column, or expressions. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2 V9.5 & db2 v9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* ENHANCE FACTORIZATION OF A COMPLEX TYPE OF OR PREDICATE. *
* *
* This fix improves the predicate factorization of OR *
* predicate *
* whose all subterms have exactly matched clause. Given an *
* example *
* predicate *
* *
* (((col1 = 1 and col2 = 2) or col1 >= 100) and col3 = 3) or *
* *
* (((col1 = 1 and col2 = 2) or col1 >= 100) and col4 = 4) *
* *
* , this fix will rewrite the predicate to *
* *
* ((col1 = 1 and col2 = 2) or col1 >= 100) and (col3 = 3 or *
* col4 = *
* 4). *
* *
* *
* *
* Here, the exactly matched clause is mixed with OR and AND. *
* The *
* comparison can be any type including >=, >, =, <, <=, IS *
* NULL, *
* IS NOT NULL, IN, etc. Both comparison operands can be *
* literal *
* including special register and host variable, single base *
* table *
* column, or expressions. *
****************************************************************
* RECOMMENDATION: *
* Please upgrde to v9.7 fixpack 1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows
|
| Solution |
Fix included in v9.7 fixpack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.06.2009
14.01.2010
14.01.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
