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

POSSIBLE WRONG RESULTS WHEN THE INPUT PARAMETERS OF AN INLINED SQL SCALAR
UDF CONTAINS AN OLAP SPECIFICATION

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When the input parameters of an inlined SQL scalar UDF contains 
an OLAP specification, and under any of the following 
situations, wrong results are possible. 
 
(1) When such UDF appears in select clause, and the select 
clause also has "distinct" keyword. 
(2) When such UDF appears in order by clause 
 
You can work around the issue by modifying the query. For 
example, if the query is: 
 
select C2 
from T1 
order by F1(min(C1) over (partition by C2)) 
 
You can modify the query to: 
 
select C2 
from 
( 
select C2, F1(min(C1) over (partition by C2)) as CC 
from T1 
) 
order by CC 
 
If the query is 
 
select distinct F1(min(C1) over (partition by c2)) * 
F1(count(C1) over (partition by c2)) 
from T1 
 
You can modify the query to: 
 
select distinct F1(CC1) * F1(CC2) 
from 
( 
select min(C1) over (partition by c2) as CC1, count(C1) over 
(partition by c2) as CC2 
from T1 
)
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************
Local Fix:
Modify the query; see "Error Description"
Solution
First fixed in DB2 10.1 Fix Pack 6
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.11.2016
02.03.2017
02.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)