Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC67423 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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.7 Fix Pack 3                                * 
****************************************************************
Local Fix:
Use 'db2 inspect' command instead of db2dart
available fix packs:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.03.2010
23.09.2010
23.09.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.3 FixList
9.7.0.3 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.