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

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
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.
Problem Summary:
**************************************************************** 
* 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 10.1 fixpack 1.                   * 
****************************************************************
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.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.06.2012
31.10.2012
31.10.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList