IBM Support

JR32385: IF YOU ENTER 24 HOURS AS THE DURATION OF AN AUTOMATIC MAINTENENANCE WINDOW IN CONTROL CENTER IT IS REALLY ZERO HOURS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 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.
    

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.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of DB2 for Linux, UNIX and Windows                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In the Configure Automatic Maintenance window                *
    * ofControlCenter, if you enter 24 hours as the duration       *
    * ofamaintenance window it is really zero hours.If you enter   *
    * 24 hours for the Duration of a maintenancewindow in the      *
    * Configure Automatic Maintenance window ofControl Center, the *
    * maintenance window 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".Click either of the buttons labelled    *
    * "Change..." next to theboxes headed "Online maintenance      *
    * window" or "Offlinemaintenance window".3) 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, whichmeansthat         *
    * automatic maintance jobs which you have configuredto run in  *
    * that maintenance window do not run.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * upgrade to DB2 V9.5 FIX PACK 5                               *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.5 Fix Pack 5.
    

Temporary fix

  • A possible workaround is to enter 23 instead of 24 as the number
    of hours for the duration of the automatic maintenance
    window.
    

Comments

APAR Information

  • APAR number

    JR32385

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-03-16

  • Closed date

    2010-03-16

  • Last modified date

    2010-03-16

  • APAR is sysrouted FROM one or more of the following:

    JR32327

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R950 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 March 2010