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.
Enable 'db2move' to change definitions during COPY SCHEMA
Using a list of schemas with db2move COPY schema function allows to copy a database content including function and procedure definitions from one database to another, And in the default mode "DDL_AND_LOAD", it copies definitions and loads data using 'load from cursor' treaing RI constraints and generated columns well. SET INTEGRITY is done automatically. And even definitions depending on another schema (like views having different schema than tables) are taken correctly, if all schemas are copied using one 'db2move' command.
BUT if definitions should be changed (e.g. directing INDEX or LOBs into own Tablespace, or introduce table partitioning), you would have to redefine and (re-)load that data manually. Although 'db2move' offers MODEs like "DDL_ONLY" and "LOAD_ONLY", the process doesn't work like the combined step. (LOAD doesn't treat all the dependencies correcty then!).
Thus db2move should be enhanced to allow the user to specify, that db2move takes a pause and prompts the user for response, before it starts with the load phase. This way defintions could be easily changed before 'db2move' load the data then.
It works well, if you change definition on the flight, while db2move is loading a different schema from the list. But it's risky, as you don't know exactly when it starts to process the definitions you want to change!
Do not place IBM confidential, company confidential, or personal information into any field.