home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC76120 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.7 fixpack 5 or later                           * 
****************************************************************
Local-Fix:
Alter the tables involved in the query to remove the volatile 
setting. 
ALTER TABLE <tabname> NOT VOLATILE
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This problem was first fixed in V9.7 Fixpack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
02.05.2011
22.12.2011
22.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList