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

SELECT OF AN CLOB COLUMN FROM AN XMLTABLE CAUSED DB2 TO CRASH.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
An example of a query that would cause the problem is: 
 
   select upi,document_id,doctext 
     from documents t1, 
     xmltable 
    ('$c/Document/documentDetailsCollection/documentDetails 
      [effectiveEndTimeStamp = 
xs:dateTime("2199-12-31T23:59:59") 
      and exists(deidentifiedDocumentText)]' 
      passing t1.xmldata as "c" 
      columns 
          doctext clob(2M) path './deidentifiedDocumentText' 
     ) as x ; 
 
  The crash will be more likely to happen when the size of the 
selected document is 87K or more. 
 
  The following error can be seen in the db2diag.log: 
 
  FUNCTION: DB2 UDB, lob manager, sqldxAppendLob, probe:608 
  MESSAGE : ZRC=0x8748006E=-2025324434=SQLDXE_BOUNDS "Value out 
of bounds" 
          DIA8600C A LOB value was out of bounds. 
  DATA #1 : unsigned integer, 4 bytes 
  4294923604 
  DATA #2 : unsigned integer, 4 bytes 
  4294923604
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* SELECT of an CLOB column from an XMLTABLE                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SELECT of an CLOB column from an XMLTABLE caused DB2 to      * 
* crash.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Install db2 v9.7 FP2                                         * 
****************************************************************
Local Fix:
Customer can break the column into multiple columns of 87K size 
or less using the substring function.  Example: 
 
select upi,document_id,doctext1,doctext2,.... 
     from documents t1, 
     xmltable 
    ('$c/Document/documentDetailsCollection/documentDetails 
      [effectiveEndTimeStamp = 
xs:dateTime("2199-12-31T23:59:59") 
      and exists(deidentifiedDocumentText)]' 
      passing t1.xmldata as "c" 
      columns 
          doctext1 clob(2M) path 
           './fn:substring(./deidentifiedDocumentText,1,86000)', 
          doctext2 clob(2M) path 
 
'./fn:substring(./deidentifiedDocumentText,86001,86000)', 
           ..... 
     ) as x ;
available fix packs:
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 6 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 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
DB2 V9.7FP2
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66524 IC74883 IC74884 IC74885 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.01.2010
17.08.2012
17.08.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList