Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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


Status Not under consideration
Created by Guest
Created on May 11, 2017

CDC should be able to read Oracle logs with asynchronous read-ahead method

Oracle archive log reading needs improving.
This customer has to process around 2.4TB / day of Redo Logs.
Due to a number of reasons there are occasional replication stops/restarts. This makes the log readers to go back in time, forcing the read of archived logs from several hours back in time.
These files are obviously not in the file system cache. an AIX PMR (15361,999,822) was opened and I/O was analyzed and measured. The I/O operations were being processed in 1-2ms (we're using a 128KB block size in CDC)
So, assuming 1ms per I/O operation, we take 32s just to read a 4GB REDO log archive. This is synchronous, so we need to add the time to actually process the log.
The same system is able to create these logs in 30s or even less at peak times. So it's easy to understand we loose ground, and it gives a very narrow margin to recover from stops.

The request is to implement asynchronous read-ahead in CDC. This would allow the I/O to be done in parallel with the log processing, so the 32s mentioned above wouldn't be "waiting time", but instead would occur simultaneously with the log processing