IBM Support

PI51231: SPACE GROWTH WAS IDENTIFIED IN V11 FOR UTS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer identified that more segments are allocated in V11 for
    UTS tablespace after several updates.
    The reason is that update module in V11 doesn't update spacemap
    entry correctly. For overflow records, update could move the
    overflow record from original overflow page to another overflow
    page. After the original overflow record is deleted from the
    original page, this original page should've been marked as
    empty('2') in spacemap page if the original overflow record is
    the only record in the original page. While in V11, those empty
    pages are marked as '3' in the spacemap page.
    If all the pages in one segment are empty pages, the whole
    segment could be marked as pseudo new segment and might be
    available to be reused before allocating a new segment. While in
    V11, segment would not be marked as pseudo new correctly as all
    pages in the segment are marked as '3' rather than '2'.
    

Local fix

  • Reorg is able to reclaim the space.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 11 for z/OS users using segmented table  *
    *                 spaces or universal table spaces.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: SPACE GROWTH was identified in UTS or   *
    *                      segmented table spaces in V11.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When updating a row in a segmented table space or an universal
    table space, if a data page becomes empty, it needs to be marked
    as empty in the corresponding data space map page. Due to a code
    bug in update code path, the page was not marked as empty in the
    space map page when it becomes empty, that prevented the page to
    be reused and caused the table space growth issue.
    

Problem conclusion

  • DB2 code has been updated to properly mark the empty data pages
    in space map pages during SQL UPDATE when the table space is
    a segmented or universal table space.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI51231

  • 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

    2015-10-26

  • Closed date

    2016-01-04

  • Last modified date

    2016-02-01

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

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

    UI34191

Modules/Macros

  • DSNIREPR
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RB10 PSY UI34191

       UP16/01/20 P F601

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":"BU053","label":"Cloud & Data Platform"},"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:
01 February 2016