|
Problem IC84457
|
Status: Closed |
A FULL SCAN OF AN MDC TABLE MIGHT BE CHOSEN WHEN THERE IS A LARGE NUMBER OF OVERFLOW RECORDS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The optimizer might favor a full scan of a multidimensional
clustering (MDC) table when there are a large number of
overflow records present in the table. Poor performance will be
noticed and the explain of the query shows a full scan of the
MDC table. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* A FULL SCAN OF AN MDC TABLE MIGHT BE CHOSEN WHEN THERE IS A *
* LARGE NUMBER OF OVERFLOW RECORDS. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 1. *
**************************************************************** |
| Local Fix: |
A reorg of the table in question will remove the overflow
records and problem can be circumvented once statistics are
collected after the reorg is performed. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
10.12.2012
10.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
