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 IC76770 Status: Geschlossen

THE OPTIMIZER DOESN'T SELECT THE TABLE THAT EXISTS IN THE COORDINATOR
NODE IN DPF FOR DYNAMIC SQL.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Create database partition group grp0 dbpartitionnums (0). 
Create database partition group grp1 dbpartitionnums (1). 
Create database partition group grp2 dbpartitionnums (2...N). 
Create tablespace cat_ts ... group grp0... 
Create tablespace ts1 ... group grp1... 
Create tablespace ts2 ... group grp2... 
Create table T.T in ts1 
Create MQT M.T in ts2 replicated. 
 
If connecting from any node from 2 to N, which doesn't have base 
table T.T but replicated MQT M.T, query optimizer should choose 
access plan to scan M.T.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Create database partition group grp0 dbpartitionnums (0).    * 
* Create database partition group grp1 dbpartitionnums (1).    * 
* Create database partition group grp2 dbpartitionnums         * 
* (2...N).                                                     * 
* Create tablespace cat_ts ... group grp0...                   * 
* Create tablespace ts1 ... group grp1...                      * 
* Create tablespace ts2 ... group grp2...                      * 
* Create table T.T in ts1                                      * 
* Create MQT M.T in ts2 replicated.                            * 
*                                                              * 
* If connecting from any node from 2 to N, which doesn't have  * 
* base                                                         * 
* table T.T but replicated MQT M.T, query optimizer should     * 
* choose                                                       * 
* access plan to scan M.T.                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.7 fixpack 6.                    * 
****************************************************************
Local-Fix:
Create tablespace replicate their MQTs across all the nodes 
except node 0 (catalog node). 
OR 
Changed TRANSFERRATE of TABLESPACE which has MQT table using 
alter tablespace.
verfügbare FixPacks:
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
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 6.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC84477 IC84664 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.06.2011
11.06.2012
11.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList