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 IT09810 Status: Geschlossen

SAPTOOLS.EXEC_CLP() ROUTINE MIGHT LEAVE A DEFUNCT PROCESS BEHIND

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The 'SAPTOOLS.EXEC_CLP()' routine might leave a defunct process 
behind after it is invoked. 
 
The parent of the defunct process will be a 'db2fmp' process. 
The reason is that the routine does not 'wait' for the child 
process to complete before leaving. 
 
A simple 'ps -edf' command would show the defunct processes with 
the ppid as the db2fmp process. 
 
The 'db2pd -fmpexechistory' command can display the routineid 
for the parent db2fmp process.  Querying the SYSCAT.ROUTINES 
system catalog table for that routineid will show if that db2fmp 
process was executing SAPTOOLS.EXEC_CLP.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5, Fix pack 7                      * 
****************************************************************
Local-Fix:
The db2fmpterm utility can be used to terminate the parent 
db2fmp process which will then terminate the defunct processes.
Lösung
First fixed in DB2 Version 10.5, Fix pack 7
Workaround
see Local Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.07.2015
03.03.2016
03.03.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList