IBM Support

PM52318: PIECESIZE OF PARTITIONED INDEX DOESN'T GET CHANGED AFTER ALTER INDEX BUFFERPOOL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer has one tablespace defined as DSSIZE 16G, pagesize 16K.
    partitioned index was defined as pagesize 4k.
    
    One part of index reached 4G limitation. Customer
    tried to alter this index to 16k bufferpool to increase
    piece size to 16G, but max piece size was still 4G after ALTER.
    

Local fix

  • drop/recreate index in larger bufferpool to get larger piece
    size.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users who alter a partitioned index  *
    *                 to use a different page size BUFFERPOOL.     *
    ****************************************************************
    * PROBLEM DESCRIPTION: After altering to use a different page  *
    *                      size BUFFERPOOL for a partitioned       *
    *                      index, the index piecesize is not       *
    *                      changed as expected. REPAIR DBD         *
    *                      DIAGNOSE/TEST reports the errors,       *
    *                                                              *
    *                      DSNU920I DSNUEDFT - OBDS DIFFER AT      *
    *                      OFFSET X'00000054' OBDINSHF             *
    *                      DSNU904I DSNUEDFT - EXISTING VALUE      *
    *                                          X'12'               *
    *                      DSNU905I DSNUEDFT - REBUILT VALUE       *
    *                                          X'14'               *
    *                                                              *
    *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
    *                      OFFSET X'0000004C' OBDPSIZE             *
    *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
    *                                          X'0012'             *
    *                      DSNU905I DSNUEDPS - REBUILT  VALUE      *
    *                                          X'0014'             *
    *                                                              *
    *                      DSNU920I DSNUEDPS - OBDS DIFFER AT      *
    *                      OFFSET X'000000C8' OBDPSRPG(2)          *
    *                      DSNU904I DSNUEDPS - EXISTING VALUE      *
    *                                          X'00040002'         *
    *                      DSNU905I DSNUEDPS - REBUILT  VALUE      *
    *                                          X'00100002'         *
    *                                                              *
    *                      Customer may receive index space full   *
    *                      message.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Altering a partitioned index to use a different page size
    bufferpool did not change the index piecesize correctly.  As a
    result, after rebuilding the indexes, the original piecesize is
    still used.
    

Problem conclusion

  • DB2 code has been changed to correctly calculate the index
    piecesize when alter partitioned index to a different page size
    buffer pool.
    
    Applying this apar will not fix indexes that have wrong piece
    size before the apar applied.  REPAIR DBD REBUILD can fix the
    incorrect OBD, rebuilding the indexes will ensure the correct
    index piecesize to be used.  Drop and re-create the index can
    also fix the problem.
    
    additional keyword: SQLALTER
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM52318

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-15

  • Closed date

    2012-01-26

  • Last modified date

    2012-03-01

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

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

    UK75738

Modules/Macros

  • DSNGDAIP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK75738

       UP12/02/11 P F202

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","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":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 March 2012