|
Problem IC77589
|
Status: Geschlossen |
DB2 CAN GENERATE A SUB-OPTIMAL QUERY PLAN FOR A TABLE THAT HAS 0 ROW YET OCCUPIES MANY EMPTY PAGES |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
Sometimes a table can have 0 row yet occupy many empty pages.
This situation can occur if you delete
all rows from a table that originally contained a lot of rows,
and you don't reorg the table afterwards.
DB2 optimizer can generate a sub-optimal query plan when such a
table is involved in a SQL statement. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All users of version 9.7 on Linux, Unix and Windows *
* platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Sometimes a table can have 0 row yet occupy many empty *
* pages. This situation can occur if you delete *
* all rows from a table that originally contained a lot of *
* rows, and you don't reorg the table afterwards. *
* DB2 optimizer can generate a sub-optimal query plan when *
* such a table is involved in a SQL statement. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V97FP5 or higher version *
**************************************************************** |
| Local-Fix: |
reorg the table |
| verfügbare FixPacks: |
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
|
| Lösung |
The APAR was fixed on DB2 V97FP5 and higher version |
| Workaround |
Reorg tables that hold empty pages. |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 18.07.2011
02.01.2012
02.01.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
