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

INCORRECT XML TEMP SUBTREE SIZE CALCULATION LEADING TO VARIOUS XML
PROCESSING ERRORS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Processing a large XML document that may require XML 
serialization can incorrectly lead to a variety of possible 
errors. 
This can happen if the XML document needs to be serialized 
internally by the DB2 server and it is stored in a temp table. 
Under specific circumstances, it may happen that a few bytes of 
a subtree in the xml document are incorrectly written out to the 
temp which can then lead to unexpected problems and errors when 
the document is reassembled from the temp storage. 
 
For example the errors may be : 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "Unknown 
Node Kind.".) 
SQLSTATE=58004 
 
During SQL processing it returned: 
SQL16129N  XML document expected end of tag "VARIANTS". 
SQLSTATE=2200M
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 5                   * 
****************************************************************
Local Fix:
There is no known workaround for this.
Solution
Problem was first fixed in DB2 Version 10.1 and Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2015
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList