|
Problem IC64708
|
Status: Closed |
DB2 CLIENT COULD CREATE DEFUNCT PROCESSES IF CLIENT AUTHENTICATION IS USED ON UNIX PLATFORM |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Connecting/attaching from a DB2 v9.5 Client and versions beyond
on Unix, creates defunct db2ckpw processes. The defunct
processes are created by the DB2 client libraries. This is an
application side problem and only occurs when one sets
authentication type to CLIENT. When the authentication occurs on
the client side, DB2 will fork db2ckpw to authenticate the user.
DB2 v9.5 and versions beyond do not install a signal handler for
SIGCHLD and therefore DB2 will not call waitpid for a child
process. However, applications such as DB2 Performance Expert
and Command Line Processor (CLP)have a handler installed for
SIGCHLD. This causes the db2ckpw process to become defunct.
The problem can be reproduced using CLP. All that is needed is
to change the DBM CFG authentication to CLIENT and use CLP to
connect/attach. A defunct db2ckpw process will be created. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using Client authentication on Unix *
****************************************************************
* PROBLEM DESCRIPTION: *
* Connecting/attaching from a DB2 v9.5 Client and *
* versionsbeyond on Unix, creates defunct db2ckpw processes. *
* Thedefunct processes are created by the DB2 client *
* libraries.This is an application side problem and only *
* occurs when onesets authentication type to CLIENT. When the *
* authenticationoccurs on the client side, DB2 will fork *
* db2ckpw toauthenticate the user. DB2 v9.5 and versions *
* beyond do notinstall a signal handler for SIGCHLD and *
* therefore DB2 willnot call waitpid for a child process. *
* However, applicationssuch as DB2 Performance Expert and *
* Command Line Processor(CLP)have a handler installed for *
* SIGCHLD. This causes thedb2ckpw process to become defunct. *
****************************************************************
* RECOMMENDATION: *
* Change the DBM CFG authentication to SERVER. *
**************************************************************** |
| Local Fix: |
Change the DBM CFG authentication to SERVER |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in DB2 v9.7 FP2. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.11.2009
31.05.2010
31.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
