IBM Data and AI Ideas Portal for Customers


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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

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

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Planned for future release
Created by Guest
Created on Jun 2, 2021

generate REDO SQL for RI actions

Hi
Our DBAs would like to have REDO statements for any RI-action generate by DB2 (e.g Delete Cascade). At the moment ALA is assuming that the RI defined on the source system also is defined on the target system.

snip from the manual:
As previously mentioned, for REDO purposes, no records marked UPD-RI

or DEL-RI will be included in the SQL. This is because the originating action

(the original SQL which caused the referential constraint SQL) is to be

re-done, which will once again activate those referential constraints, so no

extra work is needed. For UNDO purposes, those records marked as UPD-RI and

DEL-RI will be included, but only after the originating SQL is un-done. This

is necessary because referential integrity would otherwise prohibit the

activated actions without the existence of the associated parental key

values.

It could be nice to have an option to generate REDO sql for RI-actions, so we can apply this in a system with no definition of RI

We have been talking to Jorn Thyssen from Rocket software, who asked us to create an AHA

Regards. Christian Andersen fra JNDATA

Needed by Date Dec 31, 2021