|
Problem IC65358
|
Status: Closed |
INCORRECT RESULTS DUE TO WRONG TQ OPERATION PRODUCED BY NODONUMBER/DBPARTITIONNUM SCALAR FUNCTION. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - 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 *
* functioninDPFenvironment. *
****************************************************************
* 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 *
* function3. There is a DTQ below the UNION (in db2exfmt *
* output), andthedetails of the DTQ in the db2exfmt output *
* shows thefollowing:Output *
* Streams:--------------...Partitioning: (FUNC *
* )NODENUMBER() or PARTITION() directed to *
* SinglePartition...Partition Column *
* Names:----------------------+NONE *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V9.5 fixpack 6 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.5 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC65905 IC65912
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.12.2009
09.09.2010
09.09.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
