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

UNNECESSARY SQLO_BAD_USER LOGGING INTO DB2DIAG.LOG

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
You may encountering unnecessary SQLO_BAD_USER in db2diag.log
like the following:

2020-01-17-14.34.00.480708+060 I5819328E668         LEVEL: Error
PID    : 13800               TID : 47679098840832 PROC : db2sysc
0
INSTANCE: db2inst1              NODE : 000           DB  :
SAMPLE
APPHDL : 0-630               APPID: *LOCAL.db2t03.200117133407
HOSTNAME: localhost
EDUID  : 91                  EDUNAME: db2agent (SAMPLE) 0
FUNCTION: DB2 UDB, oper system services,
sqloGetUserAttribByName, probe:20
MESSAGE : ZRC=0x800F006A=-2146500502=SQLO_BAD_USER "Bad User"
         DIA8117C Error with userid "".
DATA #?1 : String, 40 bytes
getpwnam failed: user name, system error
DATA #?2 : String, 8 bytes
user1
DATA #?3 : signed integer, 4 bytes
0

The lastest v11.1 Fixpack 5 and v11.5 introduced extra logging
which caused this issue.
This APAR will reduce logging for this specific scenario.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5 m3 fp0 or later                          *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT31613 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.01.2020
24.04.2020
24.04.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)