|
Problem IC62766
|
Status: Closed |
XML QUERY RETURNS DIFFERENT NUMBER OF ROWS DEPENDING ON THE COLUMNS SELECTED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
A xml query returns different number of rows depending on the
columns selected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* In certain xmlquery where we have some nested navigation, we *
* seem to be freeing up some memory which contains important *
* information about all the query node matches and end up *
* loosing that data which leads to incorrect results. *
* *
* select account_id, usg_date from items I, *
* XMLTABLE('$d/xml/account/billsummary/section[type=200532]/sect
* passing I.easydoc as "d" COLUMNS account_id *
* varchar(100) path '../../../../../accountNumber/text()', *
* usg_date varchar(100) path 'chargeDate/text()' ) *
* as AD *
* *
* ACCOUNT_ID *
* USG_DATE *
* *
* *
* --------------------------------------------------------------
* --------------------------------------------------------------
* 8706 1027 0002 07 *
* 2009-05-28 22:11:00 *
* *
* *
* 8706 1027 0002 07 *
* 2009-06-06 07:44:54 *
* *
* *
* *
* 2 record(s) selected. <= incorrect, we should have many *
* more *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v97 Fixpack 1 *
**************************************************************** |
| Local Fix: |
Disable MEP - Multiple Extraction Points
To disable MEP set the following registry variable and then
restart the instance.
db2set DB2_COMPILER_XML_OVERRIDES=1
db2stop force
db2start |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 |
In this fix we make sure to preserve that data during navigation
and return the correct results. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.08.2009
22.02.2010
22.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
