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
See this idea on ideas.ibm.com
Our company uses DB2 zOS almost exclusively for dynamic SQL workloads. Our management expects that DB2 zOS also has high availability regarding DDL changes in this application szenario. If you intend to perform DDL changes in this environment during online operations, there are often impacts that go beyond the object to be changed. DDL changes such as DROPs of objects that are no longer required can lead to contention of other applications that have no connection whatsoever to the object to be deleted. This means that applications that are not directly affected by the change are also negatively affected by the change. If you analyze the interactions of workloads with dynamic SQL, you can often see that mainly the DBD design (a database forms a DBD and not a table) is the cause for the contentions. We expect a significant improvement in the current mechanisms of action with regard to DBDs similar to the transformation of the DB2 plan structure (transition from DBRMs to packages)
Needed by Date | Dec 31, 2020 |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Dear Norbert, The Db2 for z/OS team re-reviewed this idea and it still is not under consideration at this time. However, the team does plan to revisit this idea.
Sincerely,
Db2 for z/OS team
Is there any feedback?
kind regards
Norbert Wolf
DATEV eG
Hello Norbert, I am checking with development and will post an update when I receive their feedback.
Sincerely,
The Db2 for z/OS team
Hello,
I regularly, at least annually, check the status of my ideas. There are more than 30 votes for this idea. So it seems to be relevant for many customers. Even under V13 there is probably no solution to this. What is IBM planning to improve the problem described?
Hello Janet,
Our management expects us to be able to roll out "simple ALTERs (ALTER TABLE ADD COLUMN)" with virtually no interruptions. In some cases, we have technical DBDs in the background that are made up of many objects. In a scenario with predominantly dynamic SQL, the small ALTER TABLE ADD COLUMN change can then lead to disruptions/hinders to the applications. We can therefore not promise our management that such small changes (ALTER TABLE ADD COLUMN) will be uninterrupted.
Hello Norbert, We would like to understand the scenarios a bit better. Can you update this idea with more details about the circumstances when DBD lock contention is seen?
Thank you,
The Db2 for z/OS team
Hello,
please can you give us an update for the status of that idea? Is there something in DB2 V13 that helps in this area
We also see an increase in DBD contention. We started using CLONE tables in combination with LOAD REPLACE. We found out the hard way that the conflict on the DBD Lock, although understandable, not desirable! We now have to schedule the LOAD DATA and EXCHANGE DATA job in sequence whereas we would like to run them in parallel to improve availability of the VIEWs with UNION dependent on the tables loaded. So, a better, meaning less restricted way of handling DBD locks would be highly appreciated. We also fear that with the increasing CI/CD pipelines coming to Db2 z/OS this problem will increase as well.
Hello Norbert,
Thanks for the follow up. It's no surprise that reducing DBD contention would be a popular item. Unfortunately that does not make it any easier to do. This requirement is marked for future consideration because we have a keen interest in reducing the impact of schema changes upon the system and other application threads in particular and we continue to make progress in this area. At this point though we do not have a concrete design or roadmap in place for improving the granularity of DBDs or DBD locks. If and when that changes we will update this.
Sincerely,
Db2 for z/OS Development
Hello,
do you have any current plannings for that idea? Please can you give us an update for the status of that idea? I see 29 votes for that idea now and I think that this shows the relevance of that problem
kind regards
Norbert Wolf
Datev eG
Hello,
do you have any current plannings for that idea? Please can you give us an update for the status of that idea?
kind regards
Norbert Wolf
DATEV eG
Hello, please can you give us an update for the status of that idea?
Dear all, we've recently opened a similar idea related by the excessive DDL Locks acquisitions but on a static SQL scenario. Please vote it if you agree, https://ibm-data-and-ai.ideas.aha.io/ideas/DB24ZOS-I-1114 .