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 IC65905 Status: Closed

INCORRECT RESULTS DUE TO WRONG TQ OPERATION PRODUCED BY
NODENUMBER/DBPARTITIONNUM SCALAR FUNCTION.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
A query with nodenumber/dbpartitionnum scalar function might 
return incorrect results. The query may fail to collect rows 
from 
specified database partition(s) if all the following conditions 
are met: 
 
1.  The query involves a UNION (could also be via view with 
union or full outer join which the compiler will generate a 
union for) 
2.  At least one branch below the UNION applies a NODENUMBER or 
DBPARTITIONNUM function 
3.  There is a DTQ below the UNION (in db2exfmt output), and the 
details of the DTQ in the db2exfmt output shows the following: 
 
  Output Streams: 
  -------------- 
... 
      Partitioning:         (FUNC ) 
         NODENUMBER() or PARTITION() directed to Single 
Partition 
... 
         Partition Column Names: 
         ---------------------- 
         +NONE
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use nodenumber/dbpartitionnum scalar function in   * 
* DPF environment.                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A query with nodenumber/dbpartitionnum scalar function might * 
*                                                              * 
* return incorrect results. The query may fail to collect rows * 
*                                                              * 
* from                                                         * 
*                                                              * 
* specified database partition(s) if all the following         * 
* conditions                                                   * 
* are met:                                                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* 1.  The query involves a UNION (could also be via view with  * 
*                                                              * 
* union or full outer join which the compiler will generate a  * 
*                                                              * 
* union for)                                                   * 
*                                                              * 
* 2.  At least one branch below the UNION applies a NODENUMBER * 
* or                                                           * 
* DBPARTITIONNUM function                                      * 
*                                                              * 
* 3.  There is a DTQ below the UNION (in db2exfmt output), and * 
* the                                                          * 
* details of the DTQ in the db2exfmt output shows the          * 
* following:                                                   * 
*                                                              * 
*                                                              * 
*   Output Streams:                                            * 
*                                                              * 
*   --------------                                             * 
*                                                              * 
* ...                                                          * 
*                                                              * 
*       Partitioning:        (FUNC )                           * 
*                                                              * 
*         NODENUMBER() or PARTITION() directed to Single       * 
*                                                              * 
* Partition                                                    * 
*                                                              * 
* ...                                                          * 
*                                                              * 
*         Partition Column Names:                              * 
*                                                              * 
*         ----------------------                               * 
*                                                              * 
*         +NONE                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please apply v9.1 Fix Pack 9 or later.                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem was first fixed in Version 9.1 Fix Pack 9 (s100326).
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.01.2010
07.05.2010
07.05.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList