DB2 FOR LUW / DB2FORLUW / A50 - DB2

DB2 database might terminate abnormally in 
XMNVBUFFER::FILLRESULTBUFFER with following example stack: 
 
0x09000000147605B8 
fillResultBuffer__11XmlnvBufferFP14XmlnvNavigatorP10sqlz_valuebN 
33 + 0x6DC 
0x090000001477AF74 getTuple__14XmlnvNavigatorFRbP8sqlrr_cb + 
0xD0C 
0x090000001477AC50 getTuple__14XmlnvNavigatorFRbP8sqlrr_cb + 
0x9E8 
 
The crash as experienced by this APAR is triggered by a stack 
frame overwrite. 
 
This is indirectly caused by the XML document navigation code 
reading information from a pointer in memory which is actually 
at that point no longer valid. This is a condition that was not 
properly checked for prior to this APAR fix. 
This missing check was not in place because the conditions to 
encounter this are rare and are only encountered with specific 
XML related queries with factors like size and construct of the 
XML documents contributing to this. 
 
With the fix in place, the condition is  detected and the 
appropriate action (i.e. reading the information from the right 
location) is performed.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.5 FixPack 7.                           * 
****************************************************************

Problem was first fixed in DB2 UDB Version 10.5 FixPack 7.

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

09.09.2015
24.07.2016
24.07.2016