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

COMPILING AN UPDATE OR A DELETE SQL STATEMENT CAN RETURN SQL0901N WITH
REASON "UNABLE TO FORM A PLAN FOR ALL QUNS."

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
When compiling an UPDATE or DELETE SQL statement, DB2 can return 
error code SQL0901 with the following error message: 
 
SQL0901N  The SQL statement or command failed because of a 
database system error. (Reason "Unable to form a plan for all 
QUNs.".) SQLSTATE=58004 
 
The following conditions must be present 
(1) "REDUCE_LOCKING" is set in registry variable 
DB2_REDUCED_OPTIMIZATION 
(2) greedy join enumeration is used to compile the SQL statement 
(3) the table that is to be updated or to be deleted from is a 
correlation source of another table 
 
The following are some common scenarios of when greedy join 
enumeration is used. Note that this is not a complete list. 
- when optimization class is 0, 1, or 2 
- when stmtheap size is too small to complete dynamic 
programming join enumeration 
- when DB2_REDUCED_OPTIMIZATION has a number as the first 
component and REDUCE_LOCKING elsewhere in the registry string, 
and some additional conditions are satisfied. Please refer to 
DB2 InfoCentre for the conditions.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 4                       * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.5 Fix Pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.05.2014
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