|
Problem IC67424
|
Status: Geschlossen |
DB2DART FAILS TO IDENTIFY INITIALIZED BUT UNUSED EXTENT MAP PAGES THAT ARE CORRUPT |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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 to Version 9.8 Fix Pack 4 *
**************************************************************** |
| Local-Fix: |
Use 'db2 inspect' command instead of db2dart |
| verfügbare FixPacks: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Lösung |
First fixed in Version 9.8 Fix Pack 4 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 24.03.2010
03.08.2011
03.08.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.8.FP4
|
| Problem behoben lt. FixList in der Version |
| 9.8.0.4
|
 |
