IBM Support

PM88334: REORG 00C90101 DSNKLOD2 2005 AFTER ALTER'S

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A REORG TABLESPACE abended RC00C90101 MODDSNKLOD2 ERQUAL2005
    following this series of ALTER statements -->
    
      ALTER  INDEX       indexname NOT CLUSTER;
      ALTER  INDEX       indexname CLUSTER;
      ALTER  TABLESPACE  dbname.tsname  PART 3  COMPRESS YES;
      ALTER  TABLESPACE  dbname.tsname  PART 2  COMPRESS YES;
      ALTER  TABLESPACE  dbname.tsname  PART 1  COMPRESS YES;
      ALTER  TABLESPACE  dbname.tsname  SEGSIZE 64;
      ALTER  TABLESPACE  dbname.tsname  DSSIZE  64G;
    
    A REPAIR DBD DIAGNOSE DATABASE dbname shows values reported
    as differing for fields "OBDPIRLX" and "OBDPSRPZ".
    This indicates that the old DBD index entries were created
    prior to DB2 5.
    
    The original tablespace, prior to the alters, was a classic
    partitioned object, that was stored with 3-byte page numbers.
    After the series of alters, the REORG would convert the object
    to a Universal-Tablespace format, using 4-byte page numbers.
    

Local fix

  • A "REPAIR DBD REBUILD DATABASE dbname" will correct the problem
    and allow the REORG to run correctly.
    
    You can locate indexes, created prior to DB2 5, with this query:
    
      SELECT
        SUBSTR(CREATOR,1,8)    AS "IXCREATOR",
        SUBSTR(NAME,1,18)      AS "IXNAME",
        SUBSTR(TBCREATOR,1,8)  AS "TBCREATOR",
        SUBSTR(TBNAME,1,18)    AS "TBNAME",
        SUBSTR(DBNAME,1,8)     AS "DBNAME",
        SUBSTR(INDEXSPACE,1,8) AS "IXSPACE"
       FROM SYSIBM.SYSINDEXES
         WHERE CREATEDTS = '0001-01-01-00.00.00.000000';
    
    If this query returns index objects, then run a REPAIR DBD
    DIAGNOSE on the objects and verify that the "OBDPIRLX" and
    "OBDPSRPZ" values are seen.  If any are found, run REPAIR DBD
    REBUILD prior to running REORG.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 users who alter a partitioned table  *
    *                 space DDSIZE and this table space contains   *
    *                 partitioned indexes which are created prior  *
    *                 to DB2 Version 5.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: After alter table space DDSIZE,         *
    *                      REORGing the table space could hit      *
    *                      ABEND04E RC00C90101 at DSNKLOD2         *
    *                      ERQUAL2005.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For partitioned indexes created prior to DB2
    Version 5, 3-byte root page number is used.
    Starting from DB2 Version 5, 4-byte root
    page number is used.
    
    After DB2 was migrated, DB2 maps 3-byte root
    page number to 4-byte root page number each
    time the indexes are used. After altering
    the table space DSSIZE, the 4-byte root
    page number could be changed, mapping such
    3-byte root page number to 4-byte root
    page number could introduce incorrect
    page number which causes REORG abend.
    

Problem conclusion

  • DB2 has been changed to not map 3-byte root
    page number to 4-byte root page number after
    the root page number has been changed.
    
    Additional keywords: SQLALTER
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM88334

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-02

  • Closed date

    2013-06-27

  • Last modified date

    2013-08-02

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

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

    UK95189

Modules/Macros

  • DSNGDAIP
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK95189

       UP13/07/16 P F307

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":"10.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":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 August 2013