suche 36x36
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 IT22783 Status: Closed

INCORRECT RESULT WHEN USING THE XMLTABLE FUNCTION AND REFERENCING ELEMENTS
THAT DON"T EXIST IN THE SOURCE DOCUMENT

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
The issue is due to an incomplete fix introduced in V10.1. 
Xmltable queries like the following that reference non-existent 
tags in an XML document will return  incorrect results 
 
XMLTABLE( '$d/*:LocationUpdates'  PASSING Var_DB210_5_XML_issue 
AS  "d" 
            COLUMNS 
               SOV_LOC_ID         BIGINT      PATH 
'*:LocationId' 
              ,ORGNL_FALT         VARCHAR(2000) PATH  'let $x := 
. return $x/*[local-name()="abcd"]/*[local-name()="dabcd"]' 
)GTT;
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* XMLTABLE FUNCTIONS                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please, See Error Description and install this fix.          * 
****************************************************************
Local Fix:
a)  modified query 
 
b) don't reference any non existent tags.
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Please, See Error Description and install this fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.10.2017
16.03.2018
16.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)