DB2 - Problem description
Problem IC67422 | Status: Closed |
DB2DART FAILS TO IDENTIFY INITIALIZED BUT UNUSED EXTENT MAP PAGES THAT ARE CORRUPT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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 users * **************************************************************** * PROBLEM DESCRIPTION: * * In a DMS tablespace, when a table is created, an * * entireextentof Extent Map Pages (EMP) are initialized. * * Initially, onlythefirst page of this EMP extent is used. If * * an unused EMP pagebecomes corrupted (due to hardware * * failure), then db2dart isnotable to idenitfy this * * corruption.If this corrupt page is ever accessed, either as * * a result ofgrowing the table, reorganizing the table, or * * dropping thetable, then the database will crash with a bad * * page error. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 9.50.FP6 * **************************************************************** | |
Local Fix: | |
Use 'db2 inspect' command instead of db2dart | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.5 Fix Pack 6 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.03.2010 25.05.2010 25.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6, 9.50.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |