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

KRB5CC* FILES ARE GENERATED IN /tmp/ directory BY APPLICATION TRYING TO
CONNECT TO DB2 when pam is used.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When applications try to connect to db2, krb5cc  files are being 
written in /tmp/ directory . When connection is complete these 
files are supposed to be deleted but they are staying in /tmp/ 
directory and not getting deleted.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 systems on all Linux, Unix and Windows platforms at  * 
* service levels Version 9.7 GA  through to Version 9.7 Fix    * 
* Pack 10.                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 11 or see "Local Fix"    * 
* portion for other suggestions.                               * 
****************************************************************
Local-Fix:
The krb5cc files being generated can be safely deleted.
Lösung
The complete fix for this problem first appears in DB2 Version 
9.7 Fix Pack 11 and all the subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.12.2014
09.10.2015
09.10.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP11
Problem behoben lt. FixList in der Version
9.7.0.11 FixList