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

FED:IN PREDICATE CAN NOT BE PUSHDOWN DUE TO BLANK PADDING

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
In Predicates may not be pushdown due to blank-padding analysis. 
In trace there will following message: 
 
6016    data DB2 UDB SW- pushdown analysis sqlnd_inlist_pad_pda 
fnc (3.3.58.91.0.140) 
        pid 6301 tid 46912975661376 cpid 6523 node 0 probe 140 
        bytes 63 
 
        Data1   (PD_TYPE_HEXDUMP,55) Hexdump: 
        7075 7368 646F 776E 3D30 2069 6E20 7371    pushdown=0 in 
sq 
        6C6E 645F 696E 6C69 7374 5F70 6164 5F70 
lnd_inlist_pad_p 
        6461 2028 6E6F 7420 7661 7263 6861 7220    da (not 
varchar 
        636F 6C75 6D6E 29                          column)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use Federation Server v10.5                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Federation Server v10.5 fp4 or above              * 
****************************************************************
Local Fix:
NA
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
The problem is fixed in v10.5 fp4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.12.2013
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList