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 poor query compilation performance due to long lock list traversal in DB2 10.1 and later
Beginning with DB2 LUW 10.1 DGTT-referencing DML started to take catalog locks and therefore we have to free them and potentially traverse long lock chain if the DML is a part of a long-running transaction potentially holding millions of locks. This severely affects compile performance and as a result slows down the overall transaction. This situation is explained in CRM 04397,SGC,821 in detail.
In short, in DB2 10.1 we have moved some tablespace information out of the packed descriptor and as a result, we end up making a new call to a newly implemented SYSTABLESPACES cache.Â This call will acquire locks thus turning on the flag in DPS and triggering the necessary free_cat_locks call.Â Â Locking developers investigated the issue and determined that any change to improve performance in this area is too big to be done through a defect.
Please refer to CRM 04397,SGC,821 for more detailed analysis.
Do not place IBM confidential, company confidential, or personal information into any field.