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,
Post an idea
Upvote ideas that matter most to you
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.
ADMIN_MOVE_TABLE should immediately fail or at least warn when source table is ineligible for SWAP
Even after upgrading the database to Db2 V11.5 and beyond, older tables with check constraints and/or generated columns that were created before V9.7 will still cause the SWAP phase of ADMIN_MOVE_TABLE to fail with SQL0668N reason code 10. The underlying cause is explained in Support Documents 533327 and 143281, but why is ADMIN_MOVE_TABLE going all the way through the INIT, COPY, and REPLAY phases when the source table can't be renamed? This should be something that the utility checks for up front and issues some kind of alert to the user.
Do not place IBM confidential, company confidential, or personal information into any field.