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 IT07525 Status: Closed

INFORMATIONAL MESSAGES FROM PAM ARE LOGGED AS WARNING

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
During a connection, if PAM returns an informational message, it 
is logged as a Warning instead of an Informational message in 
the db2diag.log 
 
2015-03-05-80.00.00.000001+060 xxxx    LEVEL: Warning 
PID     : 10                TID : 1234    PROC : db2ckpwd 0 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: host1 
EDUID   : 2                    EDUNAME: db2wdog 0 [db2inst1] 
FUNCTION: DB2 UDB, oper system services, 
sqloPamAuthenticationConv, probe:7575 
MESSAGE : Permissions on the password database may be too 
restrictive. 
DATA #1 : Hexdump, 4 bytes 
0x00007FFFD3BD46A0 : 0400 0000
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW using PAM                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 FP7                                      * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 10.5 FP7
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.03.2015
26.01.2016
26.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList