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

UDF with string result types could be blocked from being pushed down

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
UDF with string result types could be blocked from being pushed 
down 
 
UDF could be blocked from being pushed down under following 
conditions: 
1. local db is in ora compatible mode (e.g. db2set registry 
DB2_COMPATIBILITY_VECTOR set to ORA) 
2. remote server's server option varchar2_compat is set to N 
3. UDF has a result type of CHAR, VARCHAR, GRAPHIC, or 
VARGRAPHIC, e.g. select myfunc.mytrim(varchar_col) from 
nickname1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platforms, all data sources                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to v101fp3                                           * 
****************************************************************
Local Fix:
Setting the server option to Y
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
v101fp3. function pushed down.
Workaround
set the server option
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.06.2013
31.10.2013
31.10.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