IBM Data and AI Ideas Portal for Customers


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2
Components Security
Created by Guest
Created on Apr 27, 2020

Provide source IP connection information on db2diag.log for all cases of SQL30082N events

Db2 not always provide the source IP connection information on db2diag.log entries, where authentication failures happens - SQL30082N

This is a regular footprint on db2diag entries, when an authentication fails to connect to the database.

2020-04-24-17.10.43.574251-420 I4421660A472 LEVEL: Warning
PID : 11731798 TID : 310814 PROC : db2sysc 0
INSTANCE: pdid605 NODE : 000 DB : PGR605D2
APPHDL : 0-12208
HOSTNAME: pdpqmd704
EDUID : 310814 EDUNAME: db2agent (PGR605D2) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 66 bytes
Password validation for user
xxxxxxxx failed with rc = -2146500507

2020-04-24-17.10.43.575127-420 I4422133A542 LEVEL: Warning
PID : 11731798 TID : 310814 PROC : db2sysc 0
INSTANCE: pdid605 NODE : 000 DB : PGR605D2
APPHDL : 0-12208
HOSTNAME: pdpqmd704
EDUID : 310814 EDUNAME: db2agent (PGR605D2) 0
FUNCTION: DB2 UDB, bsu security, sqlexSlsSystemAuthenticate, probe:150
MESSAGE : Failing connection IP address: 10.0.174.116
DATA #1 : String, 16 bytes
application id:
DATA #2 : String with size, 31 bytes
10.0.174.116.52078.200425151052

We can see the 2 distinct entries.. or providing the user ID, and a second msg, providing the source IP address from that connection attempt.

These 2 information are VITAL to assist application owners, in troubleshooting authentication failures. on Enterprise environment, shared databases used by several distinct applications, or even clustered applications, these 2 information together helps application owners to find their bad connection strings/settings and fix the issue.

But, unfortunately the source IP address is not always provided on db2diag.log .

One particular case that we found this, is when the UserID becomes invalid or revoked, as consequence of too many failed authentications.

Once the user becomes invalid or blocked by OS, Db2 does not provide the source IPs information anymore.. which brings challenges in troubleshooting the issue.

these are consecutive entries on db2diag, showing this behavior..

2020-04-23-21.05.57.995499-420 I5509A472 LEVEL: Warning
PID : 11731798 TID : 261125 PROC : db2sysc 0
INSTANCE: pdid605 NODE : 000 DB : PGR605I1
APPHDL : 0-61554
HOSTNAME: pdpqmd704
EDUID : 261125 EDUNAME: db2agent (PCMIS00I) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 66 bytes
Password validation for user xxxxxxxx failed with rc = -2146500316

2020-04-23-21.06.04.171326-420 I5982A472 LEVEL: Warning
PID : 11731798 TID : 232340 PROC : db2sysc 0
INSTANCE: pdid605 NODE : 000 DB : PGR605D2
APPHDL : 0-58371
HOSTNAME: pdpqmd704
EDUID : 232340 EDUNAME: db2agent (PGR605D2) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 66 bytes
Password validation for user xxxxxxxx failed with rc = -2146500316

2020-04-23-21.06.29.565848-420 I6455A472 LEVEL: Warning
PID : 11731798 TID : 261125 PROC : db2sysc 0
INSTANCE: pdid605 NODE : 000 DB : PGR605I1
APPHDL : 0-55853
HOSTNAME: pdpqmd704
EDUID : 261125 EDUNAME: db2agent (PCMIS00I) 0
FUNCTION: DB2 UDB, bsu security, sqlexLogPluginMessage, probe:20
DATA #1 : String with size, 66 bytes
Password validation for user xxxxxxxx failed with rc = -2146500316

As you can see, 3 consecutive failed attempts, but no source IP information was provided.

Needed by Date May 31, 2020