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

XQUERY MAY RETURN INCORRECT RESULT WHEN WHERE CLAUSE PREDICATE HAS CERTAIN
FORMAT AND XML INDEX IS USED

product:
DB2 FOR LUW / DB2FORLUW / A10 - 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 clause. It is 
bound to an expression 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 10.1 fixpack 3.                   * 
****************************************************************
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.
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
Problem was first fixed in DB2 UDB Version 10.1 FixPack 3.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.04.2013
07.10.2013
07.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 FixList
10.1.0.3 FixList