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

QUERY CONTAINING LEFT/RIGHT OUTER JOIN (LOJ), UNION ALL AND ANSI INNER JOIN
OVER DISTINCT SUBSELECT WITH LOJ MAY ABEND INSTANCE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 instance may abend if a query with the following 
characteristics is issued: 
- Contains a subselect which consumes the output of a union all 
(UA) and an ansi inner join (IJ) 
- The subselect joins the UA and IJ with a left or right outer 
join (LOJ) where the UA is a null-producer for the LOJ 
- The IJ consumes a distinct subselect (DISTSEL) 
- DISTSEL contains a left or right outer join (LOJ')
Problem Summary:
DB2 instance may abend if a query with the following 
 
characteristics is issued: 
- Contains a subselect which consumes the output of a union all 
(UA) and an ansi inner join (IJ) 
- The subselect joins the UA and IJ with a left or right outer 
join (LOJ) where the UA is a null-producer for the LOJ 
- The IJ consumes a distinct subselect (DISTSEL) 
- DISTSEL contains a left or right outer join (LOJ')
Local Fix:
Rewrite the query in question to a semantically equivalent form 
that precludes the conditions described
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 v9.7 fixpak 2
Workaround
Rewrite the query in question to a semantically equivalent form 
that precludes the conditions described
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.01.2010
13.05.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList