IBM Data and AI Ideas Portal for Customers
This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
Finding holder information for deadlocks and timeouts mainly for dynamic SQLs have been a real challenge and guessing game for us. Most of the time it is not successful. It will be great if DB2 zAI can offer more information to identify holding SQL. That will greatly help to resolve deadlock/timeout related production issues effectively.
The issue with deadlocks is that in sharing environments they sometimes appear seemingly out of nowhere. Someone implements a new query or changes an existing one, or even runs an on-request process at the wrong time, and you have deadlocks that you haven't had before. Finding the query and the user that causes the deadlock is often urgent. At the time of the deadlock, DB2 has information about both queries involved in the deadlock situation, and it knows which user/query it chooses to be a winner, and which user/query it chooses to be a victim. Providing this information to DBAs and Production Support teams in a readable, easy to use format can significantly shorten investigation time and help us make good decisions about fixing it. So thanks for bringing it up, let's hope IBM can deliver this, countless DBAs and Support Analysts will be grateful for that.
BD
Good idea!! DB2zaI have all data needed which can show the HOLDER for deadlock and timeout situation. For now DB2 only show the victors SQL statement for deadlock and timeout. It is better to show developer/DBA the holder SQL statement especially for dynamic sql execution. Developers can tune the "holder" sql to mitigate locks holding.
I agree with the description of the problem, some application teams take deadlocks very seriously and try to solve them while others simply don't care if you cannot prove a big enough customer (end user) impact. Having Db2 identify problem batch/transactions (with historical data and packages being unchanged, or something similar) would be quite helpful.