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
Allow for UNLOAD SHRLEVEL CHANGE and REORG SHRLEVEL CHANGE to be compatible wen executing on the same partition
We are running very busy environmenet with IDAA being frequently refreshed by loader with increamnts of inserted records. In addition, we are using the DB2 automated housekeeping approach with the DSNACCOX stored proc implmentation to manage and trigger all required housekeeping/maintenance actions on objects in DB2. There is often a conflict and failure of the load process observed (daily basis, up to circa 100 failures) when the UNLOAD part of idaa load hits the "utility incompatible" error due to reorg being run on the same partition which needs to be unloaded and piped into the IDAA box. etails below.
How it is impacting us - we are running a very busy environment which is highly dependent on the contents of IDAA tables which are frequently loaded. During the critical business periods we frequently insert and update a lot of key tables and at the same time, we need to keep refreshing them in IDAA. Now, of course IDAA will pull the partitions which were updated since last load and what happens also very frequently - the housekeeping kicks in and since the table was heavily updated it qualifies for REORG - on the same partitions of course. This is causing loads to often fail as the tables are often huge (billions of rows) and reorg take time etc.
Now, they all run in shrlevel change. They are not reorg discards and also they do not materialize any changes so in general, Unless it is at the switch phase - I do not see the reason to have those utilities incompatible. We can easily run select * from table during reorg, even giving partition range if we want to as it is shrlevel change. Why would UNLOAD not be able to unload the data from the source dataset and then even apply log changes to it as reorg does? I could see this synched, for example that in case reorg is in switch phase, you want allow to start new unload on the same parts as unloaded. And when unload runs in parallel, switch could just wait for it to finish if it must. Unload is in general fast enough compared with reorg so even standard delay and retry on switch could easily cater for this if there is unload already started.
Do not place IBM confidential, company confidential, or personal information into any field.