home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC89670 Status: Closed

PERFORMANCE DEGRADATION WHEN SEQUENCE IS PRESENT IN THE SELECT LIST COLUMN

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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 = ?);
Solution
First Fixed in DB2 v10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.01.2013
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)