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

DB2 MAY INCORRECTLY RETURN SQL0420N WHILE COMPILING A QUERY CONTAINING
UNION ALL OPERATORS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
DB2 may incorrectly return SQL0420N while compiling a query 
containing one or more UNION ALL operators. 
 
The UNION ALL operator(s) can either be as part of the main 
query or within subqueries.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See Local Fix or upgrade to DB2 11.1 Mod 3 Fix Pack 3        * 
****************************************************************
Local Fix:
1. Rewrite the query to avoid using UNION ALL operators. 
 
Or: 
 
2. Set the current registry variable via db2set: 
 
db2set -im DB2COMPOPT=NO_DEEPKEYPU 
 
Or for specific queries by using the following REGISTRY 
optimizer guideline: 
 
<OPTGUIDELINES> 
  <REGISTRY><OPTION NAME='DB2COMPOPT' VALUE='NO_DEEPKEYPU'/> 
</REGISTRY> 
</OPTGUIDELINES>
available fix packs:
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Fixed in DB2 11.1 Mod 3 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2017
15.03.2018
15.03.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)