DB2 - Problem description
Problem IT03123 | Status: Closed |
THE QUERY COMPILER CAN ASSUME A DEFAULT CARDINALITY FOR A CGTT | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix pack 10. * **************************************************************** | |
Local Fix: | |
After modifications are performed on the CGTT, for example, after it is populated with data, perform RUNSTATS on the CGTT | |
Solution | |
First fixed in Version 9.7 Fix pack 10. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 11.07.2014 10.11.2014 10.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |