DB2 - Problem description
Problem IT34715 | Status: Closed |
MISSING INFORMATION IN DB2DIAG.LOG WHEN USERID AND PASSWORD ARE CORRECT, BUT THE USER IS REVOKED/DISABLED/LOCKED | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
When userid/pass are correct, but the user is disabled/revoked or locked, we return the following message into db2diag.log: 2020-10-22-14.04.43.604394-240 I13087491A472 LEVEL: Warning PID : 16974450 TID : 239362 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : sample APPHDL : 0-2117 HOSTNAME: EDUID : 239362 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20 DATA #1 : String with size, 67 bytes Password validation for user batchjob failed with rc = -2146500316 When userid or password are incorrect, or expired: we see the following messages in db2diag.log: 2020-10-22-20.35.18.931385-240 I9223280A469 LEVEL: Warning PID : 27590856 TID : 164713 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-60770 HOSTNAME: HOSTNAME EDUID : 164713 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20 DATA #1 : String with size, 66 bytes Password validation for user batchjob failed with rc = -2146500507 2020-10-22-20.35.18.932215-240 I9223750A530 LEVEL: Warning PID : 27590856 TID : 164713 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : SAMPLE APPHDL : 0-60770 HOSTNAME: HOSTNAME EDUID : 164713 EDUNAME: db2agent (SAMPLE) 0 FUNCTION: DB2 UDB, bsu security, sqlexSlsSystemAuthenticate, probe:160 MESSAGE : Failing connection IP address: local IPC DATA #1 : String, 16 bytes application id: DATA #2 : String with size, 25 bytes *LOCAL.db2inst1.201023003709 we need to add the conditions to cover locked/revoked/disabled users as well. The information about IP address provides clues for customers to track down the applications using disabled users. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Users on DB2 v111m4FP5 and earlier * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First Fixed in DB2 v111m4FP6 * **************************************************************** | |
Local Fix: | |
No Local Fix | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * All Users on DB2 v111m4FP5 and earlier * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * First Fixed in DB2 v111m4FP6 * **************************************************************** | |
Comment | |
First Fixed in DB2 v111m4FP6 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.10.2020 15.03.2021 15.03.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |