|
Problem IC87073
|
Status: Closed |
XQUERY MAY RETURN INCORRECT RESULT WHEN WHERE CLAUSE PREDICATE HAS CERTAIN FORMAT AND XML INDEX IS USED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
xrquery may return incorrect results when the following
conditions are all met:
1. There is XML index created on xpath expression, called
"xpath_exp".
2. XQUERY contains a comparison WHERE predicate "a_variable"
<comp_op> "xpath_exp".
2.1. "a_variable" is a variable specified by LET or FOR clause.
It is bound to expression(s) that casts a literal value to XML
type.
2.2 <comp_op> is one out of {>, >=, <=, <}.
2.3 "xpath_exp" is placed at predicate right side. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fixpack 8. *
**************************************************************** |
| Local Fix: |
(1) Change XQUERY statement. Identify predicates falling into
condition 2's format. Rewrite predicate to "xpath_exp"
<reverse_comp_op> "a_variable".
(2) Drop XML index.
(3) If "a_variable" is from LET clause, substitute "a_variable"
with constant in comparison predicate, i.e. "<xml_type_cast>
<literal_value> <comp_op> "xpath_exp". |
| available fix packs: |
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 8. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC87106
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2012
01.04.2013
01.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
|
 |
