|
Problem IC76150
|
Status: Closed |
The DB2 fault monitor daemon is not started automatically after a new installation of DB2 V9.7 or a FixPack is done. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
After a new installation of DB2 V9.7 or a FixPack is done, the
DB2 fault monitor daemon might fail to start automatically.
Cause :
This problem is specific to Operating Systems like Solaris 10
that allows the user to start processes in specific projects
which describe the resources the process is able to use (in
/etc/project file).
In the case of such Operating System if the user has already
specified a project under which db2fmcd process
should start (ie. by adding /usr/bin/newtask -p <project> in
front of the db2fmcd path in /etc/inittab) then the entire line
gets removed from /etc/inittab by a new installation of DB2
software or a DB2 fixpak and a new line that do not contain the
newtask command will be added. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users on DB2 V9.7 FixPack 4 or below. *
****************************************************************
* PROBLEM DESCRIPTION: *
* After a new installation of DB2 V9.7 or a FixPack is done, *
* the *
* DB2 fault monitor daemon might fail to start automatically. *
* *
* *
* *
* Cause : *
* *
* This problem is specific to Operating Systems like Solaris *
* 10 *
* that allows the user to start processes in specific projects *
* *
* which describe the resources the process is able to use (in *
* *
* /etc/project file). *
* *
* In the case of such Operating System if the user has already *
* *
* specified a project under which db2fmcd process *
* *
* should start (ie. by adding /usr/bin/newtask -p <project> in *
* *
* front of the db2fmcd path in /etc/inittab) then the entire *
* line *
* gets removed from /etc/inittab by a new installation of DB2 *
* *
* software or a DB2 fixpak and a new line that do not contain *
* the *
* newtask command will be added. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 FixPack 5 or higher. *
**************************************************************** |
| Local Fix: |
Manually modify the /etc/inittab file and add the project
specific information. |
| available fix packs: |
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 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 V9.7 FixPack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.05.2011
07.12.2011
07.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
