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

HANG FOR QUERIES REFERENCING AT LEAST ONE COLUMN ORGANIZED TABLE AND WHEN
THE QUERY CONTAINS AN EXORBITANT NUMBER OF OLAP FUNCTI

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Sometimes queries may hang if those queries are referencing at 
least one Column organized table and when the query contains an 
exorbitant number of OLAP functions with incompatible partition 
by and sort requirements. 
 
Symptom will be noticed by the application becoming  stuck in 
compile state and unable to be forced off. 
 
 
The application will have the following function repeating in 
the stack dump, for example: 
 
<StackTrace> 
sqlnq_qtb20descendant_qtb_recurEPS_i 
sqlnq_qtb20descendant_qtb_recurEPS_i 
sqlnq_qtb20descendant_qtb_recurEPS_i 
sqlnq_qtb20descendant_qtb_recurEPS_i 
sqlnq_qtb20descendant_qtb_recurEPS_i 
etc.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP7                                      * 
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.08.2015
20.01.2016
20.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList