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

DB2FMCD COMMAND DOES NOT WORK IF BLANK LINES ARE APPENDED AFTER FMC ENTRY
IN /ETC/INITTAB FILE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Fault monitor entry will be inserted into /etc/inittab when we 
run ./db2fmcu command, 
Fault monitor entry should be deleted when we execute ./db2fmcd 
command. 
 
The problem is when we have a blank line immediately after fmc 
entry in /etc/inittab file, we were not able to delete the fmc 
entry (blank lines were not taken care). 
 
This caused problems during uninstall of TSM products.  This fix 
will take care of the blank lines in the /etc/inittab file.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users on V9.7 GA and FP1                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Fault monitor entry will be inserted into /etc/inittab       * 
* whenwerun ./db2fmcu command,Fault monitor entry should be    * 
* deleted when we execute./db2fmcdcommand.The problem is when  * 
* we have a blank line immediately afterfmcentry in            * 
* /etc/inittab file, we were not able to delete thefmcentry    * 
* (blank lines were not taken care).This caused problems       * 
* during uninstall of TSM products.  Thisfixwill take care of  * 
* the blank lines in the /etc/inittab file.                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FixPack 2                                    * 
****************************************************************
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
First Fixed in Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.02.2010
29.07.2010
29.07.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