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

DB2 MIGHT PRODUCE SQL0901N MESSAGE WHEN EXECUTING MULTIPLE SUBQUERIES USING
COLUMN STORE TABLES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenarios, DB2 might produce SQL0901N error message 
if the following conditions are satisfied: 
1) The query references one or more column store tables 
2) The query has two or more subqueries 
3) The subqueries can be existential or scalar subqueries 
4) There is a UNION in the query on which the subquery 
predicates are applied 
 
SQL0901N  The SQL statement or command failed because of a 
database system 
error. (Reason "Complex subquery PPD requires empty 
auxiliary_info".) SQLSTATE=58004 
 
Stack: 
sqlnr_subq_ppd_prep 
sqlnr_is_pushable_exp 
sqlnr_qun_local_ppd 
sqlnr_joinppd_rewrite 
sqlnr_joinppd_magic_detail 
sqlnr_joinppd_action 
sqlnr_comp 
sqlnr_seq 
sqlnr_rcc
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 version 105 fix pack 4                 * 
****************************************************************
Local Fix:
Solution
The problem is fixed in DB2 version 105 fix pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.04.2014
06.10.2014
06.10.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList