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

DB2 CLIENT COULD CREATE DEFUNCT PROCESSES IF CLIENT
AUTHENTICATION IS USED ON UNIX PLATFORM

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
Fixed in DB2 v9.7 FP2.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
19.11.2009
31.05.2010
31.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList