home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC65330 Status: Closed

DB2IUPDT DOES NOT UPDATE START_STOP_TIME IN WSE ENVIRONMENT.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
After running db2iupdt, dbm configuration parameter 
START_STOP_TIME is 
reset to its default value (10) in WSE environment.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 servers on Linux, Unix, and Windows platforms using  * 
* the Workgroup Server Edition (WSE) having their instance     * 
* update to v9.5 GA through Fix Pack 5.                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During instance update via db2iupdt, the value of            * 
* START_STOP_TIME is not updated and kept as the default       * 
* value.                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 9.5 Fix Pack 6.                   * 
****************************************************************
Local Fix:
Run db2 update dbm cfg to change back to previous value.
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 9.5 Fix Pack 6.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC65470 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.12.2009
25.05.2010
30.06.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP6
Problem solved according to the fixlist(s) of the following version(s)