IBM Support

IT33252: AUTOMATIC TABLE MAINTENANCE REORG RECLAIM EXTENTS OPERATIONS ON QUALIFYING ITC TABLES MAY NOT GET TRIGGERED AFTER A DB RESTART

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • The Automatic Table Maintenance evaluation of INSERT TIME
    CLUSTERED (ITC) Tables uses a methodology of first performing a
    partial evaluation of the table by checking the number of ROWS
    DELETED for the table (via MON_GET_TABLE), and only when the
    number of rows deleted meets a specific threshold, then a full
    evaluation using ADMIN_GET_TAB_INFO() is performed. This
    methodology is meant to reduce the frequency of unnecessary
    executions of ADMIN_GET_TAB_INFO() for ITC tables, which can be
    expense operations on ITC tables in terms of CPU utilization and
    locking impact to other applications which are accessing the ITC
    table.
    
    If rows are deleted from an ITC table, and, prior to the next
    automatic maintenance evaluation period, the database is
    recycled/restarted, then it is possible that an ITC table which
    is eligible for reorg-reclaim-extents (because of the rows that
    had been deleted prior to the database restart) is not
    identified as eligible for reorg. Only after subsequent delete
    activity on this table might it be identified as eligible for
    reorg.
    

Local fix

  • - The ITC will eventually qualify for reorg after subsequent
    delete activity on the table and future Automatic Table
    Maintenance evaluations.
    - Or, you can manually perform a REORG ... RECLAIM EXTENTS
    operation on the table(s).
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 Version 11.1 Mod 4 Fix Pack 6.                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 Version 11.1 Mod 4 Fix Pack 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT33252

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-18

  • Closed date

    2021-03-16

  • Last modified date

    2021-03-16

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

  • 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

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
18 March 2021