|
Problem IC89923
|
Status: Closed |
AUTOMATIC RUNSTATS MIGHT NOT EVALUATE A TABLE IF DATABASE DEACTIVATION OCCURRED WHILE THE TABLE WAS BEING PROCESSED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When AUTO_RUNSTATS is enabled for a database, evaluations to
process tables occur periodically. If the database is
deactivated while automatic runstats is processing a table,
automatic runstats might fail to evaluate the table in future
evaluations.
To check if the problem has occurred, run:
SELECT SCHEMA,NAME FROM SYSTOOLS.HMON_ATM_INFO WHERE
STATS_LOCK != 'N';
LIST UTILITIES;
The problem has occurred if:
- the SELECT query returns more than one row, or
- the SELECT query returns one row when LIST UTILITIES does not
show an active Automatic runstats
The problem can occur more frequently on, but is not restricted
to, instances with more than one database enabled for automatic
runstats. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to DB2 LUW V9.7 Fixpack 9. *
**************************************************************** |
| Local Fix: |
After a database is activated, as soon as possible before
automatic maintenance begins, typically about 2 hours after
activation, manually reset the stats_lock information:
UPDATE SYSTOOLS.HMON_ATM_INFO SET STATS_LOCK = 'N' WHERE
STATS_LOCK != 'N' |
| available fix packs: |
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 |
First fixed in DB2 LUW v9.7 FixPack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.01.2013
30.07.2014
30.07.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.9
|
 |
| 9.7.0.9
|
|
