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

ERRORNEOUS ERROR HANDLING IN SQLOLOOKUPGROUPINFOFORUSER

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Fix incorrect error message from the db2diag.log during group
lookup on windows.

When sqloLookupGroupInfoForUser, probe:209 writes a message in
db2diag.log, DATA #1 indicates the number of retry calls to
NetUserGetGroups().
If the value is smaller than the maximum retry count 3C00 0000
(=60 in decimal), it means the call was successful, so the
message should be "MESSAGE : retry Newsgroups success, retry
count:", and also, the message LEVEL should be "Warning".

2019-08-10-00.03.09.564000+540 I673748F564          LEVEL: Error
PID     : 3996                 TID : 5000           PROC :
db2syscs.exe
INSTANCE: DB2                  NODE : 000
APPHDL  : 0-18533              APPID: *LOCAL.DB2.190809150000
HOSTNAME: server1
EDUID   : 5000                 EDUNAME: db2agent (instance) 0
FUNCTION: DB2 UDB, oper system services,
sqloLookupGroupInfoForUser, probe:209
MESSAGE : retry Newsgroups failed, retry count:
DATA #1 : Hexdump, 4 bytes
0x000000F13C0599F4 : 0100 0000
....
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.09.2019
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)