|
Problem IC95311
|
Status: Closed |
THE QUERY COMPILER CAN ASSUME A DEFAULT CARDINALITY FOR A CGTT |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
In environments where real-time statistics is not enabled, if
you
do not perform runstats on a CGTT, the query compiler will use a
default cardinality estimate of 1000. This behaviour differs
from DGTTs, where the query compiler will try to estimate the
table cardinality based on the object's physical size. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Problem Description above *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.5 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
After modifications are performed on the CGTT, for example,
after it is populated with data, perform RUNSTATS on the CGTT |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 10.5 Fix Pack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
11.07.2014
11.07.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
