home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66181 Status: Geschlossen

AUTOMATIC MAINTENANCE OF RUNSTATS THROUGH CONTROL CENTER MIGHT NOT SAVE
THE THE TABLE SIZE POLICY

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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) ) )"
verfügbare FixPacks:
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

Lösung
first fixed in version 9.7 Fixpak 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.02.2010
25.05.2010
26.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.2 FixList