|
Problem IT39499
|
Status: Closed |
UNNECESSARY SQLO_BAD_GROUP LOGGING INTO DB2DIAG.LOG
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
You may encounter unnecessary SQLO_BAD_GROUP entries from
sqloGetGroupAttribByName in db2diag.log like the following:
xxxx-xx-xx-xx.xx.xx.xxxxxx-xxx I2289E757 LEVEL:
Error
PID : 20651 TID : 140323577652992 PROC :
db2sysc 0
INSTANCE: xxxxxxxx NODE : 000 DB : DB1
APPHDL : 0-24 APPID:
*LOCAL.db2inst1.211129053841
UOWID : 2 ACTID: 1
AUTHID : xxxxxxxx HOSTNAME: xxxxxxx.xxxx.xxx.xxx
EDUID : 31 EDUNAME: db2agent (DB1) 0
FUNCTION: DB2 UDB, oper system services,
sqloGetGroupAttribByName, probe:0
MESSAGE : ZRC=0x800F0069=-2146500503=SQLO_BAD_GROUP "BAD GROUP"
DIA8116C Error with group "".
DATA #1 : String, 43 bytes
getgrnam_r failed: group name, system error
DATA #2 : String, 4 bytes
user
DATA #3 : signed integer, 4 bytes
0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 systems on all Linux, Unix and Windows platforms at *
* service levels 11.1.4.5 and 11.1.4.6. Earlier releases of *
* Db2 are not affected *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.7 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All DB2 systems on all Linux, Unix and Windows platforms at *
* service levels 11.1.4.5 and 11.1.4.6. Earlier releases of *
* Db2 are not affected *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1.4.7 *
**************************************************************** |
| Comment |
The logging introduced in 11.1.4.5 did not take in to account
certain scenarios where SQLO_BAD_GROUP was an expected error
from sqloGetGroupAttribByName, such as if the named group did
not exist. This APAR reduces the logging level to INFO in those
scenarios.
If sqloGetGroupAttribByName encounters an unexpected error, this
APAR will log SQLO_GET_GROUP_ENTRY_FAILED instead of
SQLO_BAD_GROUP, and the error will be logged at ERROR level.
The complete fix for this problem first appears in DB2 Version
11.1.4.7 and all the subsequent Fix Packs. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.12.2021
17.04.2022
17.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
