IBM Support

PI12709: DB2 DOES NOT REUSE SPACE THAT HAS BEEN FREED BY ROWS THAT HAVE BEEN DELETED AND COMMITTED FOR A LONG TIME.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • It takes DB2 a long time to detect that deleted space can be
    reused, even though the delete is committed for a long time, and
    there are no active scrollable cursors. This causes the table
    space to grow and space search to take an unnecessary long time.
    ADDITIONAL SYMPTOMS:  INSERT PERFORMANCE DEGRADATION as
    available space is not reused.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL V10 and V11 DB2 for z/OS users           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Data page row IDs are not reused for    *
    *                      insert due to the presumed presence of  *
    *                      a scrollable cursor, even though there  *
    *                      are no scrollable cursors present.      *
    *                      This results in insert performance      *
    *                      degradation and unnecessary table       *
    *                      space growth.                           *
    *                      This situation can also occur when      *
    *                      an object shares a buffer pool with     *
    *                      another base table that contains        *
    *                      LOB columns in the Universal Table      *
    *                      space, LOB table space or aux index     *
    *                      table space.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    DB2 does not reuse space because it is not sensitive to
    scrollable cursors' existence.
    ADDITIONAL SYMPTOMS: RC00C9009C 00C9009C
    

Problem conclusion

  • DB2 code was changed to distinguish the existence of the
    scrollable cursor when determining row IDs reuse of the page.
    

Temporary fix

Comments

  • ×**** PE15/06/22 FIX IN ERROR. SEE APAR PI43446  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI12709

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-02-27

  • Closed date

    2015-06-03

  • Last modified date

    2015-08-26

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

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

    UI28186 UI28187

Modules/Macros

  •    DSNB1DCM DSNB1PCK DSNB1RLS DSNIDILS DSNIDLDU
    DSNIDLEO DSNIKDEF DSNIONX2 DSNIOST2 DSNIREPR DSNIRNXT DSNISGRT
    DSNISMRT DSNISRID
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UI28186

       UP15/06/19 P F506

  • RB10 PSY UI28187

       UP15/06/19 P F506

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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 March 2024