DB2 FOR LUW / DB2FORLUW / 970 - DB2

REFRESH TABLE/SET INTEGRITY FOR <table> IMMEDIATE CHECKED may 
return SQL204N when 
the following sequence of events has occurred earlier: 
 
1. <table> was originally created when CURRENT SCHEMA was set to 
a schema-name <schemaA>. 
2. CURRENT SCHEMA was then changed to another schema-name 
<schemaB>. 
3. <table> was then altered from a base table into an MQT using 
ALTER TABLE ... ADD QUERY (<MQT definition query>) 
4. <MQT definition query> mentioned in #3 references an 
unqualified table <base>. 
5. The table <schemaB>.<base> exists, but not <schemaA>.<base> 
 
Note: For #1, <table> could be initially created as a base 
table, or as an MQT that was subsequently altered into a base 
table 
 
Example: 
set current schema a; 
create table b.base (a int not null primary key, b int ); 
create table a.mqt (a int not null, b int); 
set current schema b; 
alter table a.mqt add query (select * from base where a between 
1 and 10) data initially deferred refresh immediate; 
-- The following SET INTEGRITY statement returns SQL204N 
set integrity for a.mqt immediate checked;

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 6.                            * 
****************************************************************

Specify fully qualified object names in ALTER TABLE ... ADD 
QUERY <MQT definition query> 
 
Example: 
alter table a.mqt drop query; 
alter table a.mqt add query (select * from b.base where a 
between 1 and 10) data initially deferred refresh immediate; 
set integrity for a.mqt immediate checked;

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
 

Problem was first fixed in DB2 UDB Version 9.7 FixPack 6.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84422 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

21.07.2011
06.06.2012
06.06.2012

9.7.FP6