|
Problem IC83989
|
Status: Closed |
RUNSTATS MIGHT INCORRECTLY FLAG THE TABLE TABLESPACE AS DIRTY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
RUNSTATS MIGHT INCORRECTLY FLAG THE TABLE TABLESPACE AS DIRTY.
RUNSTATS might trigger the table and/or the index tablespaces to
be marked dirty because these tablespaces contain meta data
about the database objects, and this is working as designed.
However, there is a defect in that we are marking the table
tablespace dirty in some scenarios when we should not. As an
example, if you do RUNSTATS #1, and you do not execute any
update/delete/insert activity to the table, and then you do
RUNSTATS #2 (for example, because you might want to try
different statistics options, or you might be collecting
statistics after creating an index), RUNSTATS #2 will mark the
table tablespace dirty when it need not. |
| Problem Summary: |
SUMMARY:
Users Effected:
This problem effects all users that use federated applications.
Problem Description:
RUNSTATS MIGHT INCORRECTLY FLAG THE TABLE TABLESPACE AS DIRTY.
Problem Summary:
RUNSTATS MIGHT INCORRECTLY FLAG THE TABLE TABLESPACE AS DIRTY. |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
Upgrade to DB2 Version Version 9.8, FixPak 5. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC89629
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.06.2012
17.01.2013
17.01.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.7
|
 |
