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

QUERY USING A VIEW BASED ON REPLICATED MQT IN CONTEXT OF EXISTENTIAL
SUBQUERY MAY RETURN INCORRECT RESULTS

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A query might produce incorrect results under the following 
scenario: 
 
1. The environment is a multi-partition DPF setup. 
2. There is a view which references one or more replicated MQTs 
   directly. 
3. The view is used in the context of an existential subquery. 
4. (Optional) if replicated table is maintained by user, there 
   does not exist a unique index 
 
Example: 
 
create table t1(c1 int, c2 int); 
 
create table t2(c1 int, c2 int); 
 
create table repl_mqt as (select * from t2) data initially 
deferred refresh deferred distribute by replication; 
 
create view v1 as (select * from repl_mqt); 
 
select * from v1 where v1.c2 in (select c2 from t1);
Problem Summary:
APAR fix is available in V9.7 Fixpack 5.
Local Fix:
The view should reference the base table instead of the 
replicated MQT directly.
available fix packs:
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

Solution
APAR fix is available in V9.7 Fixpack 5.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC80101 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.06.2011
12.12.2011
12.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList