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 updateson 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
Display the blocker query in Timeout/Deadlock situations
DB2 Timeouts and Deadlocks can cause significant problems for applications, and resolving them quickly is a high priority. Identifying the query that caused the deadlock or held locks long enough to cause a timeout is very important, with this info DBAs can quickly check access path and determine if we can tune it to avoid future deadlocks and timeouts.
DB2 Deadlocks and Timeouts result in SQL error -913. CQM captures information for the queries that are victims of the deadlock/timeout, but the winner/blocker queries complete successfully, and CQM doesn't make it easy for us to identify which query blocked access and caused a deadlock or a timeout.
DB2 Address Space provides the following information:
13.07.42 STC50701 DSNT375I :PZZI PLAN=DISTSERV WITH 153
So it provides the number of the blocker query in the Dynamic Statement Cache, in this case - 1663. The problem is that we can't easily dump the cache when the timeout occurs, and by the time we dump it, the statement is often not in the cache anymore.
Here is our request: when we investigate a deadlock or a timeout, we want to be able to find the blocker query in the Current SQL Activity or in the Activity Summary for the right timeslot. DB2 knows the query (in the Address space it displays query number), so we would like to either add a Query Number column to CQM output, or have another easy and intuitive way to find the blocker query text.
Considering the fact that we sometimes investigate timeouts the next business day, it is important that this info is collected and kept in CQM. OMEGAMON is not the right tool for historical info.
Do not place IBM confidential, company confidential, or personal information into any field.