|
Problem IC91395
|
Status: Geschlossen |
THE QUERY COMPILER CAN ASSUME A DEFAULT CARDINALITY FOR A CGTT |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All DB2 V10.1 on LUW users. *
****************************************************************
* 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. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V10.1 Fix Pack 3 or higher. *
**************************************************************** |
| Local-Fix: |
After modifications are performed on the CGTT, for example,
after it is populated with data, perform RUNSTATS on the CGTT |
| verfügbare FixPacks: |
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
|
| Lösung |
Fixed in DB2 V10.1 Fix Pack 3 |
| Workaround |
After modifications are performed on the CGTT, for example,
after it is populated with data, perform RUNSTATS on the CGTT |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC95311
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 06.04.2013
26.08.2014
26.08.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
