IBM Support

IC83469: INCORRECT RESULTS AFTER LOAD INTO TABLE WITH CONSTRAINTS FOLLOWED BY ATTACH OR DETACH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR fixes the following two related problems:
    
    1.  The first problem occurs after loading into a table with
    constraints and then attaching that table to a partitioned table
    before using SET INTEGRITY on the standalone table to validate
    the newly loaded data.  All rows from the newly attached
    partition should be visible after running SET INTEGRITY on the
    partitioned table, however, the newly loaded rows are not
    visible  when using an index scan.  To hit this problem there
    must be one or more partitioned indexes on the range partitioned
    table, and the source table to attach has a matching index for
    each partitioned index on the target range partitioned table.
    
    1b.  Further, if a new partitioned index is created before
    running SET INTEGRITY on the partitioned table, then the loaded
    keys will, incorrectly not be included in the new index on the
    newly attached partition.  This is a problem regardless of
    whether or not the partitioned indexes exist on the range
    partitioned table prior to attach.
    
    2.  The second problem occurs after loading into a partitioned
    table with constraints, not running SET INTEGRITY and then
    detaching one of the partitions.  All rows from the detach
    partition (i.e. the newly created standalone table) should be
    visible, however, the newly loaded rows are not visible when
    using an index scan.
    

Local fix

  • To make the loaded data visible, the user can either:
    - execute another load that loads data into the problem
    partition
    - OR execute the REORG INDEXES ALL command
    
    In order to fix the corrupted index problem mentioned in 1b, the
    user must execute the REORG INDEXES ALL command.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 10.1.0.1.                             *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in DB2 version 10.1.0.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC83469

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Installability /

  •  

    Pervasive / Serviceability / Xsystem

  • Submitted date

    2012-05-15

  • Closed date

    2012-09-13

  • Last modified date

    2012-09-13

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

    IC82921

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1"}]

Document Information

Modified date:
20 September 2021