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

QUERY WITH TABLES FUNCTIONS AND EXISTENTIAL SUBQUERY MIGHT PRODUCE SQL0901N

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Under rare scenarios, DB2 might produce SQL0901N error message 
if the following conditions are true: 
1. The query has an existential subquery 
2. The source of the subquery is a union/union all 
3. One or more branches of the union all refer to a table 
function 
 
<error message> 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "OID 
imbalance".) 
SQLSTATE=58004 
 
<stack> 
sqlnq_union_ofn_sm 
sqlnq_proc_enc 
sqlnq_qtb::add_doid 
sqlnq_sel_doid 
sqlnq_select_ofn_sm 
sqlnq_proc_enc 
sqlnq_qtb::add_doid 
sqlnr_addids 
sqlnr_EtoF_action 
 
Workaround: none
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* QUERY WITH TABLES FUNCTIONS AND EXISTENTIAL SUBQUERY MIGHT   * 
* PRODUCE SQL0901N                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First fixed in fix pack 4 of DB2 v10.5                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in fix pack 4 of DB2 v10.5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
08.09.2014
08.09.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