home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC74790 Status: Closed

DB2 MAY RETURN INCORRECT RESULTS WITH CORRELATED PREDICATE AND OLAP
FUNCTIONS IN DPF MODE

product:
DB2 FOR LUW / DB2FORLUW / 980 - 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:                                              * 
* Upgraded to DB2 version 9.8 Fix Pack 4.                      * 
****************************************************************
Local Fix:
Upgraded to DB2 version 9.8 Fix Pack 4.
available fix packs:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
Upgraded to DB2 version 9.8 Fix Pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2011
22.08.2011
22.08.2011
Problem solved at the following versions (IBM BugInfos)
9.8.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList