IBM Support

PI88777: HIGH CPU IN DBM1 ADDRESS SPACE ZIIP / ENCLAVE WHEN ZPARM ZPARM INDEX_CLEANUP_THREADS > 0

A fix is available

Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • High zIIP processor usage at
DSNILRBK+2FC (03/31/17 PI76297/UI46087) and DSNIPSFI+4260
(02/13/17 PI73408/UI44619) when Index Cleanup Threads is
active.

Local fix

  • Set ZPARM SPRMIXCU (INDEX_CLEANUP_THREADS) to zero.

Problem summary

  • ****************************************************************
* USERS AFFECTED:                                              *
* All DB2 11 and 12 for z/OS users having                      *
* indexes defined in a Segmented Table                         *
* Space and INDEX_CLEANUP_THREADS > 0                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* High CPU usage during cleanup process                        *
* of pseudo deleted index keys.                                *
****************************************************************
* RECOMMENDATION:                                              *
* Apply corrective PTF when available                          *
****************************************************************
For index defined in a segmented table space, when creating
the page set control block (PSCB) for its cleanup process
of the pseudo deleted index keys, an internal control block
will also be built for each table in this segmented table
space. If a segmented table space contains a large number
of tables (hundreds or thousands of tables), it could cause
high CPU usage to build those internal control blocks.

Problem conclusion

  • It's not necessary to access its table when cleaning up the
pseudo deleted index keys. Fixes made in DB2 to avoid building
the internal control block for each table during this cleanup
process.

Temporary fix

  • *********
* HIPER *
*********

Comments

  • ×**** PE18/01/10 FIX IN ERROR. SEE APAR PI92298  FOR DESCRIPTION
×**** PE18/01/10 FIX IN ERROR. SEE APAR PI92298  FOR DESCRIPTION

APAR Information

  • APAR number

    PI88777

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-10-12

  • Closed date

    2017-12-13

  • Last modified date

    2018-02-21

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

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

    UI52674 UI52675

Modules/Macros

  • DSNIPSFI

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RC10 PSY UI52674

       UP17/12/28 P F712 ¢

  • RB10 PSY UI52675

       UP17/12/28 P F712 ¢

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:
21 February 2018

Page Feedback