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
CDC for DB2 LUW recovering from database conditional locks
Recently one of the customers hit a conditional lock when reading from database log (with compression enabled) using DB2 read log api. Soon after this subscription failed without an ability to restart automatically.
The conditional lock failure is a result of some operation running concurrently that is getting a Z lock. For example, when IUD is followed by a specific operation like LOAD, REORG or TRUNCATE. In this case when CDC calls db2 readlogapi, it gets this lock error because those operation(s) would not have been committed yet (holding z lock on the table).
DB2 says that read log api can't read the table compression dictionary until the concurrent insert is committed hence returns the lock error to CDC.
So, this request is for enhancing the capture engine to: 1. Add retry mechanism for transient lock errors like this one. or 2. Add conditional lock errors as recoverable so that when subscription is configured as persistent it restarts automatically.
Do not place IBM confidential, company confidential, or personal information into any field.