|
Problem IC65470
|
Status: Closed |
DB2IUPDT DOES NOT UPDATE START_STOP_TIME IN WSE ENVIRONMENT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - 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.7 GA or Fix Pack 1. *
****************************************************************
* PROBLEM DESCRIPTION: *
* During instance update via db2iupdt, the value of *
* START_STOP_TIME is not updated and kept as the default *
* value. *
****************************************************************
* RECOMMENDATION: *
* Refer to local fix or upgrade to DB2 UDB version 9.7 Fix *
* Pack 2. *
**************************************************************** |
| Local Fix: |
Run db2 update dbm cfg to change back to previous value. |
| 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 |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.01.2010
30.06.2010
30.06.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.,
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
