Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC75902 Status: Closed

COMPILING AN SQL STATEMENT THAT INVOLVES VOLATILE TABLES CAN FAIL WITH
SQL0901N

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
Compiling an SQL statement can fail with SQL0901N when all of 
the following conditions are met. 
 
 
1 The SQL statement involves at least one volatile table. 
2 In the optimized SQL statement, the volatile table is joined 
with other tables on equity predicates. 
3 runstats has been done on the volatile table. 
4 The SQL statement is compiled with Inter-Partition 
Parallelism. 
5 The registry variable DB2_WORKLOAD is set to SAP. 
 
 
The SQL0901N error message contains the following text: 
 
SQL0901N  The SQL statement failed because of a non-severe 
system error. 
Subsequent SQL statements can be processed.  (Reason "Potential 
corruption in 
statistics.".)  SQLSTATE=58004 
 
The corresponding call stack can contain the following: 
 
sqlno_prds_is_NPK_adjust_eligible 
sqlno_prop_compute_cgs_join_adjust_qun 
sqlno_prop_compute_cgs_join_adjustment 
sqlno_prop_compute_cgs_adjustments 
sqlno_prop_compute_ff_adjustments 
sqlno_plan_begin_opr
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any users with volatile tables in a query                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Compiling an SQL statement can fail with SQL0901N when a set * 
* of specific conditions are met.                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 fixpack 9 or later                           * 
****************************************************************
Local Fix:
Alter the tables involved in the query to remove the volatile 
setting. 
ALTER TABLE <tabname> NOT VOLATILE
available fix packs:
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
This problem was first fixed in V9.5 Fixpack 9
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC76120 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.04.2011
27.03.2012
27.03.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.