PM42175: SUPPORT DATA SETS > 64 GB

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as new function.

Error description

  • Support data sets > 64 GB.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS customers.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: A data outage can occur if a            *
    *                      partition of a partitioned table        *
    *                      space becomes full during INSERT,       *
    *                      UPDATE, LOAD or REORG.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The maximum size of a partition that DB2 10 for z/OS
    supports is currently 64 gigabytes.
    
    If a data partition becomes full the table must be
    repartitioned.  Repartitioning distributes some of the data
    in the full partition to the other partitions.
    
    Repartitioning causes a data outage as the partitioning scheme
    of the table is modified, and the data reloaded or
    reinserted.  Repartitioning is not easily accomplished, and
    can affect applications in some cases.
    

Problem conclusion

Temporary fix

Comments

  • PM42175 provides new function that changes the maximum
    partition size or data set size to 256 GB.  Partition size
    or data size is controlled by the keyword DSSIZE on CREATE
    or ALTER.
    
    If a partition becomes full, ALTER can be used to increase
    the partition size to 128 GB or 256 GB.  REORG can be used
    to materialize the change and reload the data, thus avoiding
    an outage.
    
    The overall maximum size of a table space or index is
    not increased.  When utilizing greater than 64 GB partitions,
    the total number of partitions is decreased proportionally.
    
    The capacity of an index partition is inherited from the
    corresponding data partition.
    
    To ensure the maximum capacity of a non-partitioned index
    matches that of the table space, 128 GB and 256 GB piece sizes
    are now supported.  The piece size in K, M or G is controlled
    by the PIECESIZE keyword on CREATE and ALTER.
    
    The amount of home hash space is controlled by the HASH SPACE
    keyword.  For partitioned by range table spaces the amount of
    home hash space can be greater than 64 GB and less than 256 GB.
    
    The support is applicable to data, index on LOB and XML table
    spaces as well.
    
    Additional keywords: SQLCREATE SQLALTER SQLCODE20488 SQLCODE904
                         RC00C9009C RC00C90099 MSGDSNU398I
                         RC00E40318
    

APAR Information

  • APAR number

    PM42175

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function

  • Submitted date

    2011-06-21

  • Closed date

    2011-09-07

  • Last modified date

    2011-10-03

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

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

    UK71670

Modules/Macros

  •    DSNHSM4A DSNHSM5  DSNHSM5X DSNTIDXA DSNTIDXB
    DSN1SDEF DSN6SYSP
    

Publications Referenced
SC19298301        

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK71670

       UP11/09/22 P F109

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.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

A10

Reference #:

PM42175

Modified date:

2011-10-03

Translate my page

Machine Translation

Content navigation