DB2 - Problem description
Problem IC62102 | Status: Closed |
MATERIALIZED QUERY TABLE DEPENDANT ON DETACH RANGE PARTITIONS RETURNS WRONG RESULTS AFTER LOAD RESTART | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
1) LOAD INSERT on table fails, this table has detached RANGE Partitioned table. This table has dependant Materialized Query Table created with refresh immediate. 2) user does LOAD RESTART which succeeds, but silently corrupts the contents of the MQT because of missing index keys from detached RP table 3) SELECT on MQT from now on returns incorrect result silently because of missing index keys from detached RP table. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Version 9.5 All platforms * **************************************************************** * PROBLEM DESCRIPTION: * * 1) LOAD INSERT on table fails, this table has detached RANGE * * * * Partitioned table. This table has dependant Materialized * * Query * * Table created with refresh immediate. * * 2) user does LOAD RESTART which succeeds, but silently * * corrupts * * the contents of the MQT because of missing index keys from * * * * detached RP table * * 3) SELECT on MQT from now on returns incorrect result * * silently * * because of missing index keys from detached RP table. * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.5 Fix Pack 5 or later. * **************************************************************** | |
Local Fix: | |
None??? | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.5 Fix Pack 5. At a minimum, this fix should be applied on the server. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 20.07.2009 05.02.2010 05.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |