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 IC67210 Status: Closed

DB2 WINDOWS SERVICE CALLED "MONITORING AGENT FOR DB2" NO LONGER
AUTOSTARTED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Prior to DB2 v9.7 FP2,  a service called "Monitoring Agent for 
DB2" was set to auto-start at system boot.   This service 
supports Optim Data Administrator (formerly known as Data Studio 
Administration Console). 
 
As of DB2 v9.7 FP2,  a new install of DB2 will have this service 
set to Manual start.  Applying FP2 as a fixpack to an existing 
copy of DB2 will not change any behavior. 
 
Users of Optim Data Administrator should ensure that the service 
is set to Autostart.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows only                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Prior to DB2 v9.7 FP2,  a service called "Monitoring Agent   * 
* for                                                          * 
* DB2" was set to auto-start at system boot.   This service    * 
*                                                              * 
* supports Optim Data Administrator (formerly known as Data    * 
* Studio                                                       * 
* Administration Console).                                     * 
*                                                              * 
*                                                              * 
*                                                              * 
* As of DB2 v9.7 FP2,  a new install of DB2 will have this     * 
* service                                                      * 
* set to Manual start.  Applying FP2 as a fixpack to an        * 
* existing                                                     * 
* copy of DB2 will not change any behavior.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* If Optim Data Administrator is to be run against a DB2       * 
* instance,  ensure that the service for that instance is set  * 
* to Autostart.                                                * 
*                                                              * 
* Otherwise,  the service can be left in Manual start or       * 
* Disabled.                                                    * 
****************************************************************
Local Fix:
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
Prior to DB2 v9.7 FP2,  a service called "Monitoring Agent for 
 
DB2" was set to auto-start at system boot.   This service 
 
supports Optim Data Administrator (formerly known as Data Studio 
Administration Console). 
 
As of DB2 v9.7 FP2,  a new install of DB2 will have this 
service 
set to Manual start.  Applying FP2 as a fixpack to an existing 
copy of DB2 will not change any behavior.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2010
26.04.2010
26.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList