IBM Support

PI77164: INDEX PSEUDO DELETE CLEANUP DOES NOT PERFORM AS EXPECTED WITH ZPARM INDEX_CLEANUP_THREADS>0

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After setting the ZPARM INDEX_CLEANUP_THREADS=40 index pseudo
    delete cleanup performance was not as expected, with no
    reduction in the need for REORGs seen.
    INDEX_CLEANUP_THREADS=(any number) won't do pseudo delete
    cleanup as expected, so this apar is to make the cleanup more
    effective.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 11 for z/OS users having non zero    *
    *                 value for INDEX_CLEANUP_THREADS subsystem    *
    *                 parameter                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Index pseudo delete cleanup tasks can   *
    *                      not cleanup pseudo deleted index        *
    *                      entries effectively so the number of    *
    *                      pseudo deleted index entries continue   *
    *                      to grow over time                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Index pseudo delete cleanup tasks can cleanup the committed
    pseudo deleted index entries from the indexes. While some of the
    pseudo deleted entries are removed by the cleanup tasks, the
    tasks can not keep up with the rate that the pseudo deleted
    entries are generated. So over the time, the number of pseudo
    deleted entries in the indexes continue to grow, the indexes
    need to be reorganized to remove the pseudo deleted entries.
    

Problem conclusion

  • Index manager pseudo delete cleanup code has been updated to
    remove the committed pseudo deleted index entries more
    effectively. The wait time between each cleanup call on the same
    index is reduced.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI77164

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-23

  • Closed date

    2017-06-22

  • Last modified date

    2018-03-22

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

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

    PI77165 UI48234

Modules/Macros

  •    DSNKDAEM DSNKDAE1 DSNKDPEP DSNKGTSK DSNKTSKS
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI48234

       UP17/07/07 P F707

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
22 March 2018