IBM Support

IT30825: AUTO REORG EVALUATION MAY REPORT TABLE PARTITION SIZE EXCEEDS OFFLINE REORG SIZE CRITERIA BUT LESS THAN MAXOFFLINEREORGTABLESIZE

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If Auto Reorg excludes data partitioned tables from automatic
    reorg due to the following error:
                 TABLE EXCEEDS OFFLINE REORG SIZE CRITERIA
    
    As seen from either db2trc of the AUTO_REORG evaluation phase or
    as per the health monitor snapshots
    
    The possible cause maybe a mishandling of partition size
    determined from the catalog tables
    
    This can happen when the Table Partition is less than
    maxOfflineReorgTableSize
    
    For little endian systems a very large Data Partition size
    (larger than the 32-bit unsigned
    integer max value, 4 294 967 295) and maxOfflineReorgTableSize
    (larger than 32-bit unsigned integer value / 1024, 4 194 303) is
    required
    
    For big endian systems all partition sizes are susceptible to
    this issue
    
    Non-partitioned tables are not susceptible to this issue
    

Local fix

  • No workaround please apply fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to db2_v111m4fp6 or later                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to db2_v111m4fp6 or later
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT30825

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-11-04

  • Closed date

    2021-03-19

  • Last modified date

    2021-03-19

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

    IT30821

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
20 March 2021