|
Problem IC69398
|
Status: Closed |
DB2 MAY RETURN INCORRECT RESULTS WITH CORRELATED PREDICATE AND OLAP FUNCTIONS IN DPF MODE |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The incorrect results problem only happens in DPF mode.
This problem occurs in a query that uses OLAP functions and uses
a correlated predicate
applied to the input to the OLAP functions.
For example,
select 1
from activity a,
table(select p.actno, sum(emptime) over(partition by
p.actno) time -- OLAP function
from proj_act p left join emp_act e
on p.projno = e.projno
and a.actno = e.actno) e -- correlated
predicate
where a.actno=160
To verify that whether any query faces this problem or not,
inspect the db2exfmt output of the query.
The db2exfmt that shows the table being the parent table of the
correlation
(table activity in the example) is accessed under the processing
of the OLAP function of the query. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The incorrect results problem only happens in DPF mode. *
* *
* *
* *
* This problem occurs in a query that uses OLAP functions and *
* uses *
* a correlated predicate *
* *
* applied to the input to the OLAP functions. *
* *
* *
* *
* For example, *
* *
* *
* *
* select 1 *
* *
* from activity a, *
* *
* table(select p.actno, sum(emptime) over(partition by *
* *
* p.actno) time -- OLAP function *
* *
* from proj_act p left join emp_act e *
* *
* on p.projno = e.projno *
* *
* and a.actno = e.actno) e -- *
* correlated *
* predicate *
* *
* where a.actno=160 *
* *
* *
* *
* To verify that whether any query faces this problem or not, *
* *
* inspect the db2exfmt output of the query. *
* *
* The db2exfmt that shows the table being the parent table of *
* the *
* correlation *
* *
* (table activity in the example) is accessed under the *
* processing *
* of the OLAP function of the query. *
****************************************************************
* RECOMMENDATION: *
* Upgrading to DB2 Version 9.7 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
Upgraded to DB2 version 9.5 Fix Pack 6. |
| available fix packs: |
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 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
|
| Solution |
This problem has been fixed in DB2 Version 9.7 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.06.2010
27.09.2010
27.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
