IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
Clients:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity. http://ibm.biz/IBM-Data-and-AI-Portal-Register

Additional Information:
  • The shorter URL for this site is: https://ibm.biz/IBM-Data-and-AI-Ideas

  • To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

  • Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Requesting Q-Replication capability from Non-Temporal to Temporal Table

This RFE/Idea is to request Q-Replication capability from Non-Temporal source to Temporal Table target. The existing Q-Replication only supports from Temporal to Temporal tables. For reporting within FTM (Financial Transaction Manager), there is a need to replicate transaction data to an Operational Data Store (ODS). This is also a requirement from the legal standpoint.

To effectively meet the above requirements, we would need ability for Q-Replication to replicate data from non-temporal transactional table to temporal table on ODS.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 1 2020
  • Planned for future release
Who would benefit from this IDEA? Any customer who has need to report on historical data on Operational Data Store.
How should it work?

We request that the commit timestamp at the replication source be used by Q Apply to populate the system timestamp for the temporal table at the target. This is a more accurate representation of what-happened-when in FTM (Financial Transaction Manager).

We requested the Special Build in case # TS003658663 as a temporary work- around.

Idea Priority High
Priority Justification In the absence of this new feature/functionality, there is no practical workaround to meet the requirement.
Customer Name Huntington Bank
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    3 May 02:20pm

    Thanks for considering this, Enzo. Can triggers be federated across Db2 for LUW databases? The source (non-temporal) and target (temporal) tables are in different data centers.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    2 May 10:36pm

    a potential workaround is to create after trigger on the source and use it to generate the insert on the temporal target

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions