IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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



Add a new idea Subscribe
Status Submitted
Workspace Data Replication: Change Data Capture
Created by Guest
Created on Sep 7, 2026

RELATED IDEAS

Expose Source MySQL GTID / GTID UID in IBM CDC Replication Journal or Control Fields

Requirement / Enhancement Request:

We would like to request an enhancement in IBM InfoSphere Data Replication (CDC) for MySQL source databases to make the Source MySQL GTID / GTID UID information available at the target side as part of the CDC replication metadata, preferably through an existing or new journal/control field.

Currently, when CDC replicates transactions from a MySQL source database to a target database, the original Source MySQL GTID-based UID/transaction identification information is not available at the target side through the standard CDC replicated data or control/journal fields.

Our requirement is to capture the source GTID UID associated with each replicated transaction/record and propagate this information to the target along with the replicated data.

Business / Technical Requirement

The Source MySQL GTID information is important for:

  • End-to-end transaction traceability between source and target.

  • Identifying the exact source transaction associated with a replicated record.

  • Data reconciliation and mismatch investigation.

  • Troubleshooting CDC replication issues.

  • Validating transaction continuity during DR switchovers and switchbacks.

  • Correlating source MySQL binlog transactions with target-side CDC processing.

  • Improving auditability and operational monitoring of CDC replication.

Expected Enhancement

We request IBM CDC to provide one of the following capabilities:

  1. Expose the Source MySQL GTID / GTID UID through an existing CDC journal/control field, or

  2. Introduce a new CDC control/journal field containing the source MySQL GTID / GTID UID, or

  3. Provide another supported CDC mechanism/API through which the original MySQL source GTID can be propagated to the target.

The information should ideally be associated with each replicated transaction or record so that the target-side process can identify the corresponding source GTID.

Example

For example, if the MySQL source binlog contains a transaction with:

GTID = <source UUID>:123456

CDC currently replicates the data but does not provide this source GTID/UID information along with the target-side record.

The requested enhancement would allow the target-side CDC output/control metadata to contain the corresponding source GTID/UID, such as:

Source_GTID_UID = <source UUID>:123456

This would allow downstream applications and support teams to trace the target record back to the exact source MySQL transaction.

Environment

  • CDC Product: IBM InfoSphere Data Replication / Change Data Capture

  • Source Database: MySQL

  • Requirement: Source MySQL GTID / GTID UID propagation

  • Reference PMR: TS022902754

  • This requirement was also discussed with the LIC Management Team during the meeting held on 20 August 2026.

Requested Outcome

Please evaluate the feasibility of exposing the Source MySQL GTID / GTID UID through CDC journal/control metadata and consider implementing this capability as a product enhancement.

This functionality would significantly improve transaction-level traceability, reconciliation, monitoring, troubleshooting, and DR validation for MySQL CDC replication environments.

Reference: PMR TS022902754.

Needed By Yesterday (Let's go already!)

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.