DB2 FOR LUW / DB2FORLUW / A10 - DB2

Under certain scenarios DB2 might create a trap if the following 
conditions are true: 
1. Query with two case expressions in a select list 
2. Where one case expression contains an OLAP function like Min, 
Max and Rank 
3. Where the other case expression contains an existential 
subquery like IN, NOT IN and EXISTS 
4. One or more of the when clauses of the case expression 
contains an OLAP function 
5. One or more of the when clauses of the case expression 
contains an existential subquery 
 
Some of the known stack traces are the following: 
 
sqlnq_const_fold_treeP9sqlnq_pid 
sqlnq_exp17optimizeParseTree 
sqlnr_coleq_class_action 
sqlnr_seqPiP10sqlnr_qrwaPi 
sqlnr_rcciP10sqlnr_qrwaPi 
sqlnr_endqtb_action 
sqlnr_seqPiP10sqlnr_qrwaP14sqlnr_progressP12sqlnr_rclass 
 
 
sqlnq_const_fold_treeP9sqlnq_pid 
sqlnq_exp17optimizeParseTree 
sqlnr_selbox_mergeP9sqlnq_qtb 
sqlnr_sel_mrg_actionP10sqlnr_qrwaPi 
sqlnr_compPiiP16sqlnr_rule_state 
sqlnr_seqPiP10sqlnr_qrwa 
sqlnr_rcciP10sqlnr_qrwa

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 5                   * 
****************************************************************

Problem was first fixed in DB2 Version 10.1 and Fix Pack 5

keiner bekannt / siehe Local-Fix

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

16.07.2014
13.07.2015
13.07.2015