IBM Support

IC67423: DB2DART FAILS TO IDENTIFY INITIALIZED BUT UNUSED EXTENT MAP PAGES THAT ARE CORRUPT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a DMS tablespace, when a table is created, an entire extent
    of Extent Map Pages (EMP) are initialized. Initially, only the
    first page of this EMP extent is used. If an unused EMP page
    becomes corrupted (due to hardware failure), then db2dart is not
    able to idenitfy this corruption.
    If this corrupt page is ever accessed, either as a result of
    growing the table, reorganizing the table, or dropping the
    table, then the database will crash with a bad page error.
    

Local fix

  • Use 'db2 inspect' command instead of db2dart
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In a DMS tablespace, when a table is created, an entire      *
    * extent                                                       *
    * of Extent Map Pages (EMP) are initialized. Initially, only   *
    * the                                                          *
    * first page of this EMP extent is used. If an unused EMP page *
    *                                                              *
    * becomes corrupted (due to hardware failure), then db2dart is *
    * not                                                          *
    * able to idenitfy this corruption.                            *
    *                                                              *
    * If this corrupt page is ever accessed, either as a result of *
    *                                                              *
    * growing the table, reorganizing the table, or dropping the   *
    *                                                              *
    * table, then the database will crash with a bad page error.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade DB2 to 9.7 Fix Pack 3                                *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.7 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC67423

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-03-24

  • Closed date

    2010-09-23

  • Last modified date

    2010-09-23

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

    IC67407

  • 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

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
23 September 2010