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

DB2 DOES NOT CALL PAM_SETCRED() TO RESET THE COUNTER AFTER A SUCCESSFUL
LOGIN ON LINUX

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Linux can be configured to lock out a user after a set number of 
unsuccessful logins using the pam_tally modules. DB2 supports 
this but the counter is never decremented. This means that the 
user will get locked out even though all the connections were 
successful. DB2 needs to be modified to call pam_setcred() after 
a successful connection to reset the counter.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Users on Linux                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 Users on Linux can have their IDs locked out even though * 
* there have been no failed connection attempts.               * 
*                                                              * 
* This is because Linux can be configured to lock out a user   * 
* after a set number of unsuccessful logins using the          * 
* pam_tally modules. DB2 supports this but the counter is      * 
* never decremented. This means that the user will get locked  * 
* out even though all the connections were successful. DB2     * 
* needs to be modified to call pam_setcred() after a           * 
* successful connection to reset the counter.                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Updrate to DB2 v9.7 FP5                                      * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problem fixed in DB2 v9.7 FP5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.04.2011
02.01.2012
02.01.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList