home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IT06003 Status: Closed

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

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
Solution
The complete fix for this problem first appears in DB2 Version 
9.7 Fix Pack 11 and all the subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.12.2014
09.10.2015
09.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList