IBM Support

IC84422: REFRESH TABLE OR SET INTEGRITY ON AN MQT MAY RETURN SQL204N.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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;
    

Local fix

  • 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;
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 UDB Version 10.1                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Version 10.1 FixPack 1.                           *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 UDB Version 10.1 FixPack 1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC84422

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-14

  • Closed date

    2012-11-03

  • Last modified date

    2012-11-03

  • APAR is sysrouted FROM one or more of the following:

    IC77642

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 November 2012