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 Oct 2, 2023

Refresh table process needs ways to identify possible bootlenecks

During normal Mirroring in a subscription we have the ability to put it into monitoring and the console shows the activity and possible bottlenecks. But during refresh it's like a "black box". We have no way within the product to try to identify the cause for slow refreshes. It can be the source database, engine, network or the target engine or target repository.
In a particular situation customer stated that a refresh was around 16x slower than before. The only options we had were:
- Question the source database team to understand if there was any resource constraint.
- Check the source engine host (DB2 z/OS remote...) to see if there were any CPU or network constraints
- Check the target engine host (Kafka) for any CPU/memory constraints
- Ask customer about network and target Kafka cluster

But we got no indicator about any constraint.... we had to capture some java cores, open a case, wait for support investigation etc. just to have an idea of where the bottleneck could be.
This is not efficient, nor practical... specially when in mirroring the product provides this sort of indication in an easy way.

Needed By Quarter