DB2 FOR LUW / DB2FORLUW / A50 - DB2

Selecting an xml column using binary xml might hang or error out 
with an out of 
memory condition if the xml text for any given element is larger 
than 64k. 
 
While selecting xml column in binary with text content larger 
than 64k, 
you may see the program looping and receive the following or 
similar errors: 
 
- java.io.IOException: org.xml.sax.SAXException: ERROR: 
Incorrect document identifier 
- java.io.IOException: org.xml.sax.SAXException: ERROR: 
Unexpected marker 77 Byte Offset: 179005 
- com.ibm.db2.jcc.am.DisconnectRecoverableException: 
[jcc][t4][2091][11332][4.19.26] Attempt to fully materialize lob 
data that is too large for the JVM. Disable data source property 
"fullyMaterializeLobData" for locator-based lob implementation. 
ERRORCODE=-4499, SQLSTATE=nul 
 
 
The APAR fixes two byte integer overflowing in an xml 
serialization code path.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms.                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.5 Fixpack 7 or later.                 * 
****************************************************************

First fixed in DB2 LUW v10.5 Fixpack 7.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

03.06.2015
10.02.2016
10.02.2016