home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC62961 Status: Closed

XMLTABLE RETURNS PARTIALLY DUPLICATED RESULT WHEN THE DATA EXTRACTED
IS EXTRACTED AS CLOB

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
XMLTABLE may return partially duplicated result when the data 
extracted is extracted as CLOB, when the data length is longer 
than 1800 bytes.  The resulting data looks like it is 
duplicated, but the last few bytes of the first occurence of the 
data are missing. 
 
A sample query that might result in such error is: 
 
SELECT Y.* 
  FROM SYSIBM.SYSXSROBJECTCOMPONENTS AS X, 
  XMLTABLE ( 
    XMLNAMESPACES('http://www.ibm.com/xmlns/prod/db2/xdb1' AS 
"xdb", 
                  'http://www.ibm.com/xmlns/prod/db2/mon'  AS 
"mon"), 
    '$d/xs:schema/xs:annotation/xs:appinfo/xdb:table' 
    passing XMLPARSE(DOCUMENT X.COMPONENT STRIP WHITESPACE) as 
"d" 
    COLUMNS 
     CREATESTMT    CLOB(32672)      PATH 
'upper-case(normalize-space(mon:createStmt/text()))' 
     ) AS Y; 
 
The problem will not happen if CLOB(32672) in the above query is 
replaced with VARCHAR(32672).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* see error description in APAR                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to V97 fixpack 1                                     * 
****************************************************************
Local Fix:
Use VARCHAR instead of CLOB when the expected result is greater 
than 1800 bytes
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
this problem is fixed in V97 fixpack 1
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC63849 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.09.2009
16.02.2010
16.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 FixList