|
Problem IC91760
|
Status: Closed |
A QUERY WITH CORRELATION AND FLOWING XML DATA MIGHT PRODUCE INCORRECT RESULTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - 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 10.1 fix pack 3. *
**************************************************************** |
| 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 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 |
First fixed in version 10.1 fix pack 3. |
| Workaround |
See Local Fix. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
17.10.2013
17.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
|
 |
| 10.1.0.3
|
|
