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 Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Submitted
Workspace Informix
Components Informix Server
Created by Guest
Created on Mar 7, 2023

Speed control for 'cdr sync'

'cdr sync' is a very fast and efficient way of creating a copy of a table when used with loopback replication. The problem is that it can be too quick and can create logical logs at a rate that can overwhelm replication and log backups.

The idea is to have some kind of brake that would be in operation when either the number of logical logs not backed up or the number of logs not shipped to a HDR or RSS server exceeds a threshold. We anticipate this threshold would be quite low and designed to avoid any significant lag. The brake would stop 'cdr sync' from generating new log records until replication and log backups catch up. It is quite possible that the brake would be applied and released many times during a sync.

Use of the brake would be optional (possibly a new onconfig parameter).

Needed By Quarter
  • Guest
    May 5, 2023

    Is this meant for 'cdr sync' target, or rather source or both?

    I'd assume not too many log records should be created on source side?