|
Problem IC64704
|
Status: Geschlossen |
IF YOU ENTER 24 HOURS AS THE DURATION OF AN AUTOMATIC MAINTENENANCE WINDOW IN CONTROL CENTER IT IS REALLY ZERO HOURS |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
In the Configure Automatic Maintenance window of Control Center,
if you enter 24 hours as the duration of a maintenance window
it is really zero hours.
If you enter 24 hours for the Duration of a maintenance window
in the Configure Automatic Maintenance window of Control Center,
the maintenance window is really zero hours.
Consequently, automatic maintenance jobs (such as runstats and
reorg) do not run.
To reproduce the problem you can do the following steps.
In Control Center, highlight the name of a database, then right
click, and
select "Configure Automatic Maintenance...".
A window with the title "Configure Automatic Maintenance" should
appear.
In the "Configure Automatic Maintenance" window click the button
labelled "3. Timing".
Click either of the buttons labelled "Change..." next to the
boxes headed
"Online maintenance window" or "Offline maintenance window".
A window whose title begins "Change Maintenance Window
Specification" should appear.
In that window enter 24 as the number of hours in the Duration
field.
Then click the OK button.
Now in the "Configure Automatic Maintenance" window the value
for "Time"
for the maintenance window includes "(24 hours)".
But really the maintenance window is zero hours, which means
that automatic maintance jobs which you have configured to run
in that maintenance window do not run. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 for Linux, UNIX and Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* In the Configure Automatic Maintenance window of *
* ControlCenter, if you enter 24 hours as the duration of *
* amaintenance window it is really zero hours.Consequently, *
* automatic maintenance jobs (such as runstatsand reorg) do *
* not run.To reproduce the problem you can do the following *
* steps.1) In Control Center, highlight the name of a *
* database, thenright click, and select "Configure *
* AutomaticMaintenance...".2) A window with the title *
* "Configure Automatic Maintenance"should appear.In the *
* "Configure Automatic Maintenance" window click thebutton *
* labelled "3. Timing".3) Click either of the buttons labelled *
* "Change..." next tothe boxes headed "Online maintenance *
* window" or "Offlinemaintenance window".4) A window whose *
* title begins "Change Maintenance WindowSpecification" should *
* appear.In that window enter 24 as the number of hours in *
* theDuration field.Then click the OK button.Now in the *
* "Configure Automatic Maintenance" window thevalue for "Time" *
* for the maintenance window includes "(24hours)".But really *
* the maintenance window is zero hours, which meansthat *
* automatic maintance jobs which you have configured torun in *
* that maintenance window do not run. *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local-Fix: |
A possible workaround is to enter 23 instead of 24 as the
number of hours for the duration of the automatic maintenance
window. |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in Version X Fix Pack Y |
| Workaround |
A possible workaround is to enter 23 instead of 24 as the number
of hours for the duration of the automatic maintenance window. |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 19.11.2009
08.03.2010
08.03.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.1
|
 |
