DB2 FOR LUW / DB2FORLUW / A50 - DB2

Certain SQL with NOT EXISTS clause can cause the engine to trap 
or cause a SQL901N error. 
 
Example stack output might be : 
 
000007FED210CCB8 offset: 0000000000000118 in 
<sqlng_prepare_SUBQ_operation> 
000007FED20219C3 offset: 0000000000000323 in 
<sqlng_build_SBQR_op> 
000007FED210BBF6 offset: 0000000000001CA6 in 
<sqlng_process_parse_tree_node> 
000007FED2109C1C offset: 00000000000000FC in 
<sqlng_process_BF_node> 
000007FED2108CF8 offset: 0000000000000318 in 
<sqlng_walk_BF_chain> 
000007FED20A8086 offset: 00000000000001B6 in 
<sqlng_build_thread> 
000007FED2024863 offset: 00000000000017F3 in 
<sqlng_build_CASE_op> 
000007FED210BBC7 offset: 0000000000001C77 in 
<sqlng_process_parse_tree_node> 
000007FED2109C1C offset: 00000000000000FC in 
<sqlng_process_BF_node> 
000007FED211378F offset: 000000000000015F in 
<sqlngScalarExpressionBuilder::buildExpression> 
000007FED2112ADF offset: 000000000000003F in 
<sqlngExpressionBuilder::buildExpression> 
000007FED210D238 offset: 0000000000000148 in 
<sqlng_walk_EXPR_chain> 
000007FED20A8D52 offset: 0000000000000E82 in 
<sqlng_build_thread> 
000007FED203B071 offset: 0000000000000441 in 
<sqlng_process_mate_op> 
000007FED1FE4560 offset: 00000000000000C0 in 
<sqlngProcessLolepop> 
000007FED203A529 offset: 00000000000001E9 in 
<sqlng_process_pipe_op> 
000007FED1FE4560 offset: 00000000000000C0 in 
<sqlngProcessLolepop> 
000007FED2069D8E offset: 00000000000002DE in 
<sqlng_process_return_op> 
000007FED1FE4560 offset: 00000000000000C0 in 
<sqlngProcessLolepop> 
000007FED20A8053 offset: 0000000000000183 in 
<sqlng_build_thread> 
000007FED1FE5DE4 offset: 0000000000001664 in <sqlng_main> 
 
000007FED2145E52 offset: 0000000000001402 in <sqlnn_cmpl> 
 
000007FED2144A3C offset: 000000000000003C in <sqlnn_cmpl> 
 
000007FED3542F86 offset: 00000000000002D6 in <sqlrr_cmpl>

**************************************************************** 
* 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:

15.09.2015
21.01.2016
21.01.2016