DB2 - Problem description
Problem IC87767 | Status: Closed |
A QUERY WITH CORRELATION AND FLOWING XML DATA MIGHT PRODUCE INCORRECT RESULTS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
You might encounter incorrect results produced from a query that retrieves data from an XML column or produces XML data using constructs such as XMLELEMENT, and contains one or more correlated subqueries. This problem is more likely to occur in a partitioned database environment if the correlated subquery is not collocated to the other table(s) in the query, requiring a table queue in the correlation path in the access plan generated by the DB2 optimizer. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users using XML data * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 8. * **************************************************************** | |
Local Fix: | |
If your query is using XML functions to aggregate a list of string values, you can avoid this problem by using the LISTAGG function. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First fixed in version 9.7 Fix Pack 8 | |
Workaround | |
See Local Fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91760 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.11.2012 20.04.2013 20.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |