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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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
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
Do not place IBM confidential, company confidential, or personal information into any field.