IBM Support

PI14975: "MAXIMUM EXTENTS REACHED" ERROR WHEN RUNNING ONLINE REORG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Running Online REORG with Utilities Enhancement Tool causes
    "Maximum extents reached" error to occur on the dataset of index
    which was created on the mapping table by Utilities Enhancement
    Tool. There is no way to specify a large PRIQTY SECQTY to avoid
    this problem.
    .
    This also fixes -911 errors due to deadlock
    and timeout on the single mapping table tablespace
    when running multiple REORG SHRLEVEL CHANGE utility
    jobs concurrently.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Utilities Enhancement Tool.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Running Online REORG with Utilities     *
    *                      Enhancement Tool causes                 *
    *                      "Maximum extents reached" error to      *
    *                      occur on the dataset of index which     *
    *                      was created on the mapping table by     *
    *                      Utilities Enhancement Tool. There is    *
    *                      no way to specify a large PRIQTY        *
    *                      SECQTY to avoid this problem. This also *
    *                      fixes -911 errors due to deadlock       *
    *                      and timeout on the single mapping       *
    *                      table tablespace when running multiple  *
    *                      REORG SHRLEVEL CHANGE utility jobs      *
    *                      concurrently.                           *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI14975

  • Reported component name

    DB2 UTIL ENHANC

  • Reported component ID

    5655T5800

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-04-01

  • Closed date

    2014-07-07

  • Last modified date

    2014-08-04

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

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

    UI19378

Modules/Macros

  •    ABPRUSQL ABPSINIT ABPSUSQL ABPUMAIN
    

Fix information

  • Fixed component name

    DB2 UTIL ENHANC

  • Fixed component ID

    5655T5800

Applicable component levels

  • R220 PSY UI19378

       UP14/07/15 P F407

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSCVQTD","label":"IBM Db2 Administration Tool for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.2.0"}]

Document Information

Modified date:
12 February 2021