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 Delivered
Created by Guest
Created on Sep 30, 2014

Latency aware query offload decision

BdB has 2 active Accelerators with several replicated tables (meaning 2 subscriptions on CDC z/OS side). BdB already has scripts to synchronize the Load process in both Accelerators, but the replication may have different latencies. When a query on replicated tables is accelerated, it may run in different Accelerators in a short period of time, giving "inconsistent" results due to the latency difference.
I used the term "inconsistent" result here to mean that once the query is resolved with more up-to-date data (short CDC latency), if resolved again with less up-to-date data (long CDC latency) then it is like having its data being "regressed".
A way to solve this would be to have DB2 Optimizer deciding to what accelerator to send the query based on the most up-to-date replication for the given table(s).
  • Guest
    Reply
    |
    Jan 10, 2019

    Shipped in V7.