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

ENFORCE USAGE OF REPLICATED TABLES IN A DATA PARTITIONING FEATURE
(DPF) ENABLED DATABASE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
In a Data Partitioning Feature (DPF) enabled database, users 
have the option of replicating their tables in a partition 
group. 
 
For a query referencing a Base Table (BT) that has 1 or more 
dependent Replicated Table(s) (RT), the Optimizer decides on the 
usage of any RT(s) in the final access plan based on costing. 
 
Users wishing to enforce usage of RTs, regardless of the 
Optimizer's costing decisions, may do so with a registry 
variable (REGVAR), which can be specified as follows: 
 
db2set DB2_EXTENDED_OPTIMIZATION=FORCE_REPLICATED_MQT_MERGE 
 
Other values for the DB2_EXTENDED_OPTIMIZATION REGVAR can be 
combined with this one by separating them with commas. 
 
Note that with the REGVAR set, if there are multiple dependent 
RTs or Materialized Query Tables (MQT) for a BT, the first found 
RT will be used and all other dependent objects ignored.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* EE or EEE                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 1.                       * 
****************************************************************
Local Fix:
Manually alter any affected queries by referencing applicable 
RT(s) directly.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 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 10 for Linux, UNIX, and Windows

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