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 IC89670 Status: Geschlossen

PERFORMANCE DEGRADATION WHEN SEQUENCE IS PRESENT IN THE SELECT LIST COLUMN

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Under rare scenarios, performance degradation might be noticed 
if the following conditions are true: 
 
1. There is a sequence present in the output column of select 
list 
2. There are two or more tables in the subselect directly below 
the sequence 
 
eg. 
select SEQUENCE1.NEXTVAL, col1, col2 
from table1 t1 
where t1.col1 = 
   (select MAX(col1) 
   from table1 t1 
   where col2 = ?);
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users on DB2 v10.1 FP2 and lower                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP3                                     * 
****************************************************************
Local-Fix:
Separate the sequence into a new subselect: 
 
select SEQUENCE1.NEXTVAL , col1, col2 
from 
(select * 
from table1 t1 
where t1.col1 = 
   (select MAX(col1) 
   from table1 t1 
   where col2 = ?);
Lösung
First Fixed in DB2 v10.1 FP3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
21.01.2013
10.10.2017
10.10.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version