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
Fix timeout errors during pending alter materialization reorgs
We're using DB2 z/OS V10 and tried using pending alter for making online schema change on an SAP table to increase a PBG table's DSSIZE from 4 GB to 64 GB. When we ran the SHRLEVEL CHANGE reorg to implement the pending alter, the reorg caused SAP transactions to get timeout errors against DSNDB06.SYSTSTSP. The problem was reported to IBM but we were told DB2 was working as designed.
The explanation we received was a pending alter materialization REORG needs to perform schema definition changes in the SWITCH phase. This requires invalidation of plans/packages/dynamic statement cache, and blockage of static/dynamic SQL from coming in while the REORG is changing the objects' definition. As a result, the traditional DRAIN ALL behavior performed on non-pending-alter materializing REORG is not sufficient (the IRLMRWT value is used). The dependency manager serializes the process of invalidating packages that takes place when DDL changes are made. There is no granularity on the type of change being implemented and each package or dynamic statement are invalidated serially.
We want SHRLEVEL CHANGE reorgs that materialize pending alters to have no impact to work being done by our business transactions.
Do not place IBM confidential, company confidential, or personal information into any field.