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

DB2 MIGHT PRODUCE ABEND OR PRODUCE SQL0901N WHEN EXECUTING A RECURSIVE
QUERY WITH A JOIN ON EXPRESSIONS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under rare scenarios, DB2 might abend or produce SQL0901N when 
the following conditions are true: 
1) DB2 must be running on MPP configuration 
2) The query contains a recursive UNION ALL construct 
3) The recursive branch of the UNION ALL contains one or more 
join predicates 
4) Atleast one of the joins is of type: <expression> = <col>, 
where <expression> involves only columns from a single subselect 
eg. T1.C1 + T1.c2 + 1 = T2.c1
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* MPP                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 Fix Pack 5 or higher.            * 
****************************************************************
Local Fix:
Manually rewrite the query to push the expression to the 
subselect and use the output column reference for join predicate
Solution
Problem first fixed in DB2 version 10.1 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.03.2015
26.07.2015
26.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList