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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Submitted
Created by Guest
Created on Jan 17, 2024

IDAA V7: Distinction between Replication and Log reading for ISYNC feature

Idea is based on CASE TS011806661 - IDAA V7: Replication latency is growing when replication is stopped (despite the fact no table is defined for the replication)

From the technical perspective of the IDAA team, the issue lies in the perception that replication itself is experiencing delays. In reality, the delays are more accurately attributed to the time required for reading logs, which is an essential activity for various purposes, including tracking schema modifications and ensuring feature functionality.

In light of recent customer feedback, there is a suggestion to make a clear distinction in the IDAA replication messaging. The customer expresses a preference for separate notifications: one indicating replication delays and another specifically highlighting delays in log reading. This distinction aims to provide users with a more accurate understanding of the system's status, allowing them to differentiate between delays associated with replication activities and those linked to log-reading processes.

Needed By Quarter