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:
  • 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.

Additional Information:
  • The shorter URL for this site is:

  • To view our 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.

Rollback changes to both accelerators if failure occurs loading multiple accels in one load statement

We have a situation where it is important to keep the data in synch on both accelerators, so we use one statement to load both accelerators.

Real case: The data is loaded from OPERLOG logstream to shadow table every 15 minutes on two IDAA accelerators. To avoid loading duplicate data, we only load the newest rows that have been written to the logstream since the last time the load ran. To ensure this, we select the max timestamp from table in IDAA and then load the rows from the logstream that are greater than the max timestamp into IDAA. This works well unless the load to one accelerator fails and the other is successful. Then the max timestamps aren't the same on both accelerators and there is potential for either a gap or duplicates to occur next time the loads run, since we aren't guaranteed which accelerator the job will retrieve the max timestamp from.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 2 2020
  • Planned for future release
Who would benefit from this IDEA? Having a reliable max timestamp to trust will prevent potential duplicates or gaps of missing data when loading to IDAA
How should it work?

Provide an option so that if one of the loads fails, the overall job fails. The changes should be rolled back from the successful load to keep the two accelerators in synch. It needs to be flexible enough that the option can be turned off if necessary. If an accelerator is down for an extended period of time, the customer may want the option of continuing to load one accelerator.

Idea Priority Medium
Customer Name Mark Kaiser
  • Attach files

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