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 (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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 https://ideas.ibm.com


Status Submitted
Created by Guest
Created on Nov 13, 2024

For tables w/ columns that are generated by default, update the internal sequence with the next value for the column

When using Qrep for DR , we have to make the target table which has generated numeric values to be generated by default.  That is understood. 
In a DR scenario, when we fail over from the A to the B side, we have to run a script that gets the max value for the column and issue an "alter table <tabname> alter column <colname> restart with <max value +1>".  If not the following happens:
1) Table get created on both the A side and B side and replication is set up with numeric generated column COL1
2) Table A gets 100 rows loaded so COL1 next value is 101.  Data is replicated to B side
3) We have a DR event and apps that write are pointed to the B side
4) If an app writes to the table on the B side, the next generated column value for COL1 is 1 , not 101.  The data insert would fail if COL1 is the primary key.

Why is this needed ?  When using Qrep for DR where HADR is not an option (ex. DPF systems) , we can automate the failover of apps that write to the database instead of having to write a script that update the generated columns.   In some cases where ETL apps try to write to the B side after a failover, we can prevent data corruption. 

Needed By Yesterday (Let's go already!)