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
UOW size for mass delete on table with data capture
requesting that DB2 generate reasonably sized URs when performing a mass delete action against a table with DATA CAPTURE set to CHANGES. in a specific case, we were rotating partitions on a base source table which was being replicated with data capture - but when the Alter table occurs to rotate the partition, the purging of the data is propagated via db2 logs as deletes to the target through CDC. when rotating partitions, you would expect to be able to purge that data without replicating it to target table - however, in our case, it pushed through the entire contents of the partition as a single delete statement to CDC which overloaded it's staging space and brought down our LPAR as it exhausted aux storage because the single UOW was too large to process. need to be able to control the size of the uow as you are replicating deletes from an alter statement that is rotating partitions.
Do not place IBM confidential, company confidential, or personal information into any field.