IBM Support

IC99228: DB2PD -REORG MIGHT SHOW INCORRECT REORG END TIME FOR PARTITIONED TABLES

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When reorg is run on one partition of a partitioned table (ON
    DATA
    PARTITION clause) the reorg end time is updated for all
    partitions, including those which were not reorganized.
    
    If reorg is run on all partitions, the reorg end time gets
    updated
    only when the last partition is finished (hence the end time is
    the
    same for all partitions).
    
    Reorg end time can be checked by db2pd tool using -reorg switch.
    
    Example:
    # reorg on all partitions
    $ db2  "reorg table my_partitioned"
    $ db2pd -reorg -db sample
    [...]
    Table Reorg Stats:
    Address            TableName          Start               End
    [...] Status
    0x0700000044147CA8 MY_PARTITIONED     01/22/2014 05:53:54
    01/22/2014 05:53:59  [...] Done
    0x0700000044148FA8 MY_PARTITIONED     01/22/2014 05:53:58
    01/22/2014 05:53:59  [...] Done
    0x07000000441469A8 MY_PARTITIONED     01/22/2014 05:53:54
    01/22/2014 05:53:59  [...] Done
    
    # reorg on one partition
    $ db2 "reorg table my_partitioned on data partition PART1"
    $ db2pd -reorg -db sample
    [...]
    Address            TableName          Start               End
    [...] Status
    0x0700000044147CA8 MY_PARTITIONED     01/22/2014 05:56:40
    01/22/2014 05:56:43  [...] Done
    0x0700000044148FA8 MY_PARTITIONED     01/22/2014 05:53:58
    01/22/2014 05:56:43  [...] Done
    0x07000000441469A8 MY_PARTITIONED     01/22/2014 05:53:54
    01/22/2014 05:56:43  [...] Done
    
    As we can see, end time was updated for all partitions despite
    the fact that reorg was run only on partition 1
    

Local fix

  • Actual time of REORG end can be verified using LIST HISTORY
    command:
    $ db2 LIST HISTORY REORG CONTAINING "<SCHEMA>.<TABLE>" FOR
    <DB_NAME>
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 version 9.7 and Fix Pack 10 or higher.        *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 version 9.7 and Fix Pack 10.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC99228

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-02-07

  • Closed date

    2014-11-10

  • Last modified date

    2014-11-10

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

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

    IT02442 IT02447

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC99228

Modified date: 10 November 2014