home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT02177 Status: Geschlossen

DB2FMCU -D TERMINATED WITH SIGTERM AND RETURN CODE 143

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Execution of 'db2fmcu -d' may terminate with return code 143. 
Following will be displayed in the DB2 command line upon 
execution of db2fmcu: 
 
# /db2/SB2/db2sb2_home/sqllib/bin/db2fmcu -d 
Terminated 
# echo $? 
143 
 
db2fmcu uses operating system call fcntl to check if file 
'/var/db2/.fmcd.lock' is locked by a running instance of the DB2 
fault monitor deamon (db2fmcd). 
If the file is locked a kill is sent to the PID returned by 
fcntl to finish the running db2fmcd process. 
 
It's been observed that the operating system might return PID 0 
for a locked file when fcntl is called. This could happen if the 
file is locaked on a shared filesystem (e.g. nfs). If the file 
is locked by a running process on machine A a call to fcntl on 
machine B will return the information that the file is locked 
but the PID will be 0. 
 
In case fcntl returns PID 0 db2fcmu does a kill against the 
process group and therefore terminates itself. 
This is not expected, hence db2fmcu needs to check the returned 
PID. A running db2fmcd process will always have a PID larger 
than 0.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 FixPack 10.                       * 
****************************************************************
Local-Fix:
Lösung
First fixed in DB2 version 9.7 FixPack 10.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.06.2014
17.11.2014
17.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP10
Problem behoben lt. FixList in der Version
9.7.0.10 FixList