|
Problem IC77468
|
Status: Closed |
DB2 CAN GENERATE A SUB-OPTIMAL QUERY PLAN FOR A TABLE THAT HAS 0 ROW YET OCCUPIES MANY EMPTY PAGES |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* 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: *
* Please upgrade to DB2V95FP9 or higher *
**************************************************************** |
| Local Fix: |
reorg the table |
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The problem was fixed on DB2V95FP9 or higher |
| Workaround |
reorg the table. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC77589
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.07.2011
12.03.2012
12.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
