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

RHEL 7: THE DB2 FAULT MONITOR FEATURE DOES NOT SUPPORT THE SYSTEMD INIT
SYSTEM

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
In Red Hat Enterprise Linux 7, systemd replaces upstart as the 
default init system. The DB2 fault monitor does not support the 
systemd init system. During execution of db2fmcu, instead of 
expected systemd configuration, db2fmcu creates an entry in the 
deprecated /etc/inittab file. 
 
You can observe symptoms in OS strace. Once you execute: 
 
./db2fmcu -u -p /opt/ibm/db2/V11.1/bin/db2fmcd 
 
In the trace snippet you can see: 
 
readlink("/etc/inittab", 0x7ffff54f82e0, 4094) = -1 EINVAL 
(Invalid argument) 
access("/etc/.inittab.lock", F_OK) = 0 
open("/etc/.inittab.lock", O_WRONLY|O_CREAT, 0644) = 3 
fcntl(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=0, 
len=0}) = 0 
readlink("/etc/inittab", 0x7ffff54f8190, 4094) = -1 EINVAL 
(Invalid argument) 
access("/etc/inittab", F_OK) = 0 
... 
 
The goal of this APAR is to introduce support for systemd by the 
DB2 fault monitor.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Db2 RHEL 7 users                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 V11.1 Mod 1 Fix Pack 1                        * 
****************************************************************
Local Fix:
Create file: /etc/systemd/system/db2fmcd.service with following 
content: 
 
[Unit] 
Description=DB2V111 
 
[Service] 
ExecStart=/opt/ibm/db2/V11.1/bin/db2fmcd 
Restart=always 
KillMode=process 
KillSignal=SIGHUP 
 
[Install] 
WantedBy=default.target 
 
 
Next execute: 
 
systemctl enable db2fmcd 
systemctl start db2fmcd
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
Fixed in Db2 V11.1 Mod 1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.10.2016
09.10.2017
28.10.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
11.1.1.1 FixList