Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC71579 Status: Closed

DB2 INSTANCE SERVICE IS NOT STARTED AUTOMATICALLY AFTER THE DB2 PRODUCT IS
UPGRADE FROM LOWER FIX PACK LEVEL

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
In a DB2 copy where multiple DB2 products were installed, eg. 
ESE + QP, the instance service's Startup type was set as 
"Automatic". 
After the DB2 products are upgraded to a higher fixpak level, 
eg. from V95GA to V95FP6, the instance service is not started, 
and its startup type is reset to "Manual". 
 
The same problem does not happen if there is only one DB2 
product in the DB2 copy, where the instance service will be 
started after the fixpak upgrade, and its Startup type will not 
be changed.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V95 on windows                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In a DB2 copy where multiple DB2 products were installed,    * 
* eg. ESE + QP, the instance service's Startup type was set as * 
* "Automatic".                                                 * 
* After the DB2 products are upgraded to a higher fixpak       * 
* level, eg. from V95GA to V95FP6, the instance service is not * 
* started, and its startup type is reset to "Manual".          * 
*                                                              * 
* The same problem does not happen if there is only one DB2    * 
* product in the DB2 copy, where the instance service will be  * 
* started after the fixpak upgrade, and its Startup type will  * 
* not be changed.                                              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The following are the options you can take to work-around    * 
* the problem:                                                 * 
* (1). Start the db2 instance, by executing the db2start       * 
* command;                                                     * 
* (2). Go to the Services wizard from Control Panel -->        * 
* Administratiive Tools. Select the DB2 instance service,      * 
* change its Startup type back to "Automatic" and then start   * 
* it                                                           * 
*                                                              * 
* As the fix will be implemented in V95FP7, the other option   * 
* is to upgrade to v95fp7 (or higher)                          * 
****************************************************************
Local Fix:
The following are the options you can take to work-around the 
problem: 
(1). Start the db2 instance, by executing the db2start command; 
(2). Go to the Services wizard from Control Panel --> 
Administratiive Tools. Select the DB2 instance service, change 
its Startup type back to "Automatic" and then start it
available fix packs:
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
Will be fixed in V95 FP7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.09.2010
15.11.2010
15.11.2010
Problem solved at the following versions (IBM BugInfos)
9.5.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.7 FixList
9.5.0.7 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.