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

INSTANCE DEFUNCT PROCESSES CREATED UPON LOADS

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
This involves loads using file_transfer_cmd causing db2vend 
process to become defunct as follows: 
 
1. We don't wait for completion of userexit in db2vend (we don't 
call wait nor waitpid after fork and exec in sqloexecs). 
2. Neither set its SA_NOCLDWAIT flag nor set SIGCHLD to SIG_IGN 
as the result of resetting SIGCHLD to default with FILE TRANSFER 
COMMAND option in db2load utility.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Load                                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Defunct processes from loads                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Cust wait for interim/ applied WA                            * 
****************************************************************
Local Fix:
By using LOGARCHMETH1 TSM setting, we no longer call userexit as 
a child process of db2vend process, so the first condition will 
be no longer satisfied. Hence, the problem will be resolved.
available fix packs:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
APAR created - Set LOGARCHMETH1 as WA
Workaround
not known / see Local fix
Comment
Set LOGARCHMETH1 as WA
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.07.2011
05.08.2011
05.08.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.4 FixList