home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC75678 Status: Geschlossen

GROUP BY CLAUSE ON COLUMNS FROM ONE SOURCE INSIDE A SUBSELECT MAY NOT BE
PUSHED DOWN IF THE SUBSELECT IS USED IN AN OUTER JOIN

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
A GROUP BY clause specified on columns from a single source may 
not be fully optimized under certain conditions, which are: 
- The GROUP BY clause is used in a subselect 
- The subselect is used in an OUTER JOIN 
- The GROUP BY clause only groups columns from a single source 
- At least one of the columns in the GROUP BY clause defines 
uniqueness 
- The source of the columns is used in a join 
- All columns referenced in the output list of the subselect are 
simple, i.e., are not used in any expressions
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A GROUP BY clause specified on columns from a single source  * 
* may                                                          * 
* not be fully optimized under certain conditions, which are:  * 
*                                                              * 
* - The GROUP BY clause is used in a subselect                 * 
*                                                              * 
* - The subselect is used in an OUTER JOIN                     * 
*                                                              * 
* - The GROUP BY clause only groups columns from a single      * 
* source                                                       * 
* - At least one of the columns in the GROUP BY clause defines * 
* uniqueness                                                   * 
*                                                              * 
* - The source of the columns is used in a join                * 
*                                                              * 
* - All columns referenced in the output list of the subselect * 
* are                                                          * 
* simple, i.e., are not used in any expressions                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5 or later.              * 
****************************************************************
Local-Fix:
The issue can be worked around by include one or more columns in 
the output list of the subselect in a no-op (no-operation) 
expression. 
For example, an integer column (c1) used in the output list of a 
subselect could be re-written as (c1+0).
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 9.7 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
07.04.2011
07.12.2011
07.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList