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

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

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
Solution
First fixed in DB2 Version 10.5, Fix pack 7
Workaround
see Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.07.2015
03.03.2016
03.03.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList