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 IC91690 Status: Closed

QUERY WITH NUMEROUS PARAMETER MARKERS IN AN IN LIST HANGS DURING
COMPILATION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
A query that has a very large number of parameter markers in an 
IN LIST may hang during query compilation. 
 
For example: 
    select * from T where C1 in (?,?,?,...)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW version v10.1 fixPack 3                   * 
****************************************************************
Local Fix:
Rewrite the IN LIST to use a subselect: 
    select * from T where C1 in ( select cast( val as <type> ) 
from ( values ?,?,?,... ) inlist(val)
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 LUW version v10.1 fixPack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.04.2013
11.11.2013
11.11.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList