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

DB2 CAN RETURN SQL0901N WHEN COMPILING SQL STATEMENTS ACCESSING TABLES WITH
GENERATED COLUMNS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
DB2 can return SQL0901N when compiling SQL statements. The error 
code contain the following message: 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "Bad Plan; 
Unresolved QNC 
found".)  SQLSTATE=58004 
 
The SQL statements should meet the following conditions: 
 
1. The SQL statement access tables which contain generated 
columns 
2. The SQL statement has join predicates that reference the 
columns on which the generated column is based 
3. The generated column is not explictly referenced in the SQL 
statement
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running DB2 v9.5                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 can return SQL0901N when compiling SQL statements. The   * 
* error                                                        * 
* code contain the following message:                          * 
*                                                              * 
*                                                              * 
*                                                              * 
* SQL0901N  The SQL statement failed because of a non-severe   * 
*                                                              * 
* system error.                                                * 
*                                                              * 
* Subsequent SQL statements can be processed.  (Reason "Bad    * 
* Plan;                                                        * 
* Unresolved QNC                                               * 
*                                                              * 
* found".)  SQLSTATE=58004                                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* The SQL statements should meet the following conditions:     * 
*                                                              * 
*                                                              * 
*                                                              * 
* 1. The SQL statement access tables which contain generated   * 
*                                                              * 
* columns                                                      * 
*                                                              * 
* 2. The SQL statement has join predicates that reference the  * 
*                                                              * 
* columns on which the generated column is based               * 
*                                                              * 
* 3. The generated column is not explictly referenced in the   * 
* SQL                                                          * 
* statement                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7 FP5.                                     * 
****************************************************************
Local Fix:
Add the generated column to the SQL statement.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.05.2011
31.05.2011
31.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)