DB2 - Problem description
Problem IC67407 | Status: Closed |
DB2DART FAILS TO IDENTIFY INITIALIZED BUT UNUSED EXTENT MAP PAGES THAT ARE CORRUPT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
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. | |
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.1 Fix Pack 10 * **************************************************************** | |
Local Fix: | |
Use 'db2 inspect' command instead of db2dart | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Solution | |
Problem was first fixed in Version 9.1 Fix Pack 10 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67422 IC67423 IC67424 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 23.03.2010 13.06.2011 13.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.10 |