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

XML QUERIES WORKING WITH XML SEQUENCES MAY RETURN INCORRECT RESULTS.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Depending on the data, XML query may return incorrect results. 
 
Here is a sample result. In this case, the count() should return 
100. 
 
$ db2 import from data.del of del xml from xmls insert into 
transact 
$ db2 -tvf a.txt 
SELECT count(id) FROM TRANSACT WHERE 
xmlexists('$root/transact[action/assignor/@loginNameResponseCode 
="573076-1" and @transactState=1]' passing data as "root") 
 
1 
----------- 
         91 
 
  1 record(s) selected. 
 
$ db2 -tvf b.txt 
SELECT count(id) FROM TRANSACT WHERE 
xmlexists('$root/transact[action/assignor/@loginNameResponseCode 
="573076-1"]' passing data as "root") and 
xmlexists('$root/transact[@transactState=1]' passing data as 
"root") 
 
1 
----------- 
        100 
 
  1 record(s) selected. 
 
$ db2 -tvf d.txt 
SELECT count(id) FROM TRANSACT WHERE 
xmlexists('$root/transact[./action/assignor/@loginNameResponseCo 
de="573076-1" and @transactState=1]' passing data as "root") 
 
1 
----------- 
        100 
 
  1 record(s) selected. 
 
$ db2 -tvf c.txt 
SELECT count(id) FROM TRANSACT WHERE 
xmlexists('$root/transact[@transactState=1 and 
./action/assignor/@loginNameResponseCode="573076-1"]' passing 
data as "root") 
 
1 
----------- 
        100 
 
  1 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 DB2 Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
13.11.2012
13.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList