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,
Post an idea
Upvote ideas that matter most to you
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.
We had a situation with an automatic process that got it's password expired and begun failing to login to DB2. This process had around 35 threads and all of them where trying to connect to DB2 in an infinite loop. It was having around 5000 authentication requests per minute.
We are using transparent LDAP authentication on AIX, against IBM GSA solution.
After a couple of hours we noticed that DB2 was taking up to 10 minutes to authenticate remote users or local users that where executing "db2 connect to DB_NAME user USER_NAME"
This happened 2 times, first time we have recycled DB2 and it worked fine for some hours, and second time we contacted the client and asked it to stop the processes, after that, DB2 got back to normal.
We where told by support team that there's no way to prevent this ar DB2 level, so better to open a RFE
Also we where trying to implement some monitoring on the diaglogs to block IP's at AIX FW level if they are having a malignant behavior
But I had a problem with messages "-2146500508= SQLZ_RC_PSWEXP" as for this cases when the password is expired, DB2 only reports the User and not the IP into the diaglog.
For others like "-2146500507=SQLZ_RC_BADPSW" or "-2146500502=SQLZ_RC_BADUSR" it reports the user in one message and the IP in the following message, but for *508, it does not have those 2 parts, and we are having some problems detecting from which IP it's coming from, same happened during our problem, we needed to search for the user into ldap, then into w3, then contact the user, then his manager and his team, and toke us like 2 hour to detect the IP where this process was comming from.
Do not place IBM confidential, company confidential, or personal information into any field.