|
Problem IC65912
|
Status: Closed |
INCORRECT RESULTS DUE TO WRONG TQ OPERATION PRODUCED BY NODONUMBER/DBPARTITIONNUM SCALAR FUNCTION. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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 *
* inDPF environment. *
****************************************************************
* PROBLEM DESCRIPTION: *
* A query with nodenumber/dbpartitionnum scalar function *
* mightreturn incorrect results. The query may fail to collect *
* rowsfromspecified database partition(s) if all the *
* followingconditionsare met: *
* *
* 1. The query involves a UNION (could also be via view *
* withunion or full outer join which the compiler will *
* generate aunion for) *
* 2. At least one branch below the UNION applies a *
* NODENUMBERorDBPARTITIONNUM function *
* 3. There is a DTQ below the UNION (in db2exfmt output), *
* andthedetails of the DTQ in the db2exfmt output shows the *
* following: *
* Output Streams: *
* -------------- *
* ... *
* Partitioning: (FUNC ) *
* NODENUMBER() or PARTITION() directed to SinglePartition *
* ... *
* Partition Column Names: *
* ---------------------- *
* +NONE *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V9.7 fixpack 2 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 6 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 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 |
Problem was first fixed in Version 9.7 Fix Pack 2 (s100514). |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.01.2010
06.07.2010
06.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
