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
Option to override LOAD utility maintaining MAXASSIGNEDVAL for identity columns in Db2 V12
Our existing process to move data from one region to another using the LOAD utility stopped working on tables with generated by default as identity key column after we upgraded to Db2 12. The new LOAD enhancement to maintain MAXASSIGNEDVAL is causing issues and we need an option to override or disable this new feature at the LOAD utility level.
Db2 12 introduced the LOAD utility to maintain MAXASSIGNEDVAL for user-provided input, and this new feature is enforced with LOAD REPLACE and LOAD RESUME YES.
Prior to Db2 12, LOAD utility did not update MAXASSIGNEDVAL.
This is how it works now under Db2 V12:
If input file has identity column value higher than MAXASSIGNEDVAL in the Catalog, LOAD updates MAXASSIGNEDVAL with the higher value.
If input file has identity column value lower than MAXASSIGNEDVAL in the CATALOG, LOAD does not update MAXASSIGNEDVAL.
This design work fine with LOAD REPLACE as data gets replaced with the input file, but it does not always work with LOAD RESUME YES when input file gets added to the existing data.
With LOAD RESUME YES, MAXASSIGNEDVAL does not necessarily represent the maximum value. Table can potentially have identity key column value higher than the input file and MAXASSIGNEDVAL in the Catalog.
When LOAD utility updates MAXASSIGNEDVAL based on what's in the input file that shows higher than MAXASSIGNEDVA catalog but table actually has higher value than the input file , it will create -803 errors.
To mitigate this issue, we need an option to disable or override the new behavior with LOAD utility.
Do not place IBM confidential, company confidential, or personal information into any field.