Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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

Status Planned for future release
Components Q Replication for Z
Created by Guest
Created on Sep 14, 2017

LOAD should not be restarted when Apply fails during SET INTEGRITY

When setting up Replication for a DB2 Table for the first time Apply will use a LOAD FROM Cursor to do an initial copy of the tables data. If there are constraints or generated columns defined for that table Apply will issue a SET INTEGRITY command after the load successfully finishes.
If this SET INTEGRITY command fails, eg. because it runs into a deadlock, Apply will re-issue the LOAD command although that was run successfuly.
This is not necessary - re-issuing the SET INTEGRITY commad would be sufficient.
This current behaviour can lead to very long runtimes for the initial setup of a tables replication, means the replicated table is not available at the earliest possible time.