DB2 - Problem description
Problem IC75416 | Status: Closed |
RUNSTATS via USE PROFILE collects inaccurate statistics after REDISTRIBUTE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
You may notice that table cardinality is calculated wrong when using statistics profile on a table after adding database partition(s) and performing a redistribute. The statistics collection (RUNSTATS) during REDISTRIBUTE does not update the user statistics profile's number of nodes. On the subsequent RUNSTATS USE PROFILE, DB2 looks at the user statistics profile number of nodes as indication of how many nodes the table is on. This causes incorrect external catalog statistics. In contrast the internal table packed descriptor cardinality value is correct. Hence this issue affects tools like REORGCHK, which is using the external statistics stored in the catalog tables. This issue does not affect the query compiler which relies on statistics stored in the internal packed descriptor of the table. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
Local Fix: | |
Running an RUNSTATS 'update profile' or setting a new statistics profile after the REDISTRIBUTE helps to correct the number of nodes in the profile and get the correct table cardinality. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 9.7 Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.03.2011 12.12.2011 12.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |