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
Improve INDOUBT thread processing in two-phase commit scenario
Recently we had a pretty severe production outage on an 8-way data sharing group. After resolution of the root cause, WAS and Db2 z were quite slow in recovery. Following the crash, there were dozens of indoubt threads and lots of retained locks as well. The indoubt thread handling did not complete as expected, resulting in retained locks continuing to be held and indoubt threads still persistent until WAS transaction logs were wiped clean and the WAS servers restarted. The threads in question were involved in two-phase commit (2PC) processing, with WAS as the commit coordinator and Db2 as a participant.
The proposal is to improve the way indoubt thread processing is handled for 2PC transactions such that if a coordinator (Db2) completes its portion of the 2PC work, it should be resolved as far as Db2 is concerned. In our case, we performed RECOVER INDOUBT ACTION(COMMIT) commands and all the threads showed as COMMITED-H. Following that, we ran RESET INDOUBT to clear the indoubt thread information from Db2. However, when WAS had an intact transaction log, we were not able to return Db2 to "normal" status due to persistent retained locks and indoubt threads. We belive that even though the work was committed heuristically, Db2 was still waiting for confirmation to do so from the commit coordinator, and that confirmation was never coming.
We're basically looking for Db2 (as a participant in 2PC) to have the ability to manage its portion of the global transaction in a recovery scenario like this. rather than having to wait on the commit coordinator.
Do not place IBM confidential, company confidential, or personal information into any field.