Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC65358 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
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

Lösung
Problem was first fixed in Version 9.5 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC65905 IC65912 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.12.2009
09.09.2010
09.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version