|
Problem IC80160
|
Status: Closed |
DB2PD -RUNSTATS SHOWS INCORRECT "END TIME" FOR A USER RUNSTATS IF A SUBSEQUENT AUTOMATIC RUNSTATS IS DONE TO THE SAME TABLE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When you issue a RUNSTATS command, you can check its progress
with the -runstats option of db2pd. The information continues
to be available after the RUNSTATS completes. If automatic
statistics collection subsequently processes the same table, the
end time information is incorrectly modified. If you use db2pd
-runstats to review your collection again, you might think the
collection took longer than it really did. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.5 Fix Pack 10. *
**************************************************************** |
| Local Fix: |
Review the statistics logs for information on statistics
collections. |
| Solution |
This problem was first fixed in DB2 Version 9.5 Fix Pack 10. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.12.2011
23.10.2012
23.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.10
|
 |
