|
Problem IC66181
|
Status: Closed |
AUTOMATIC MAINTENANCE OF RUNSTATS THROUGH CONTROL CENTER MIGHT NOT SAVE THE THE TABLE SIZE POLICY |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
In DB2 version 9.1 and above, there is a new table size value
that can be specified to control which tables are to be
considered for automatic maintenance of runstats and reorg
through Control Center.
This table size limit policy will not be saved if you set this
value for a database that was migrated from version 8 to
version 9. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users that migrates from version 8 to version 9 using *
* automatic maintenance of runstats. *
****************************************************************
* PROBLEM DESCRIPTION: *
* In DB2 version 9.1 and above, there is a new table size *
* value that can be specified to control which tables are to *
* be considered for automatic maintenance of runstats and *
* reorg through Control Center.This table size limit policy *
* will not be saved if you set this value for a database that *
* was migrated from version 8 to version 9. *
****************************************************************
* RECOMMENDATION: *
* Rebuilding the objects that are required for a "POLICY" *
* and"AM" will solve the issue.To do so, perform the *
* following.db2 "CALL SYSINSTALLOBJECTS( *
* 'POLICY','D','USER04K1',CAST(NULL AS VARCHAR(128) ) )"db2 *
* "CALLSYSINSTALLOBJECTS( 'POLICY', 'C','USER04K1',CAST(NULL *
* ASVARCHAR(128) ) )" *
**************************************************************** |
| Local Fix: |
Rebuilding the objects that are required for a tools POLICY and
AM will solve the issue.
db2 "CALL SYSINSTALLOBJECTS( 'POLICY', 'D', 'USER04K1', CAST(
NULL AS VARCHAR(128) ) )"
db2 "CALL SYSINSTALLOBJECTS( 'POLICY', 'C', 'USER04K1', CAST(
NULL AS VARCHAR(128) ) )" |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
first fixed in version 9.7 Fixpak 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.02.2010
25.05.2010
26.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
