IBM Data and AI Ideas Portal for Customers

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:

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

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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Aug 3, 2018

Preserve table creation timestamp after reorg-finsished using admin_move_table procedure (online table move)

Following Knowledge Center,
we perform table reorg using admin_move_table . The issue is, after run admin_move_table command, the original table creation timestamp is not preserved, which is a different behavior comparing with classic offline and online inplace reorg both of which preserve the table creation timestamp in the system catalogs. Also other industry RDBMS preserve the table creation timestamp after online table move operation.
  • Guest
    May 28, 2021

    Could this behavior (resetting or preserving a table's CREATE_TIME) be controlled by a setting in the options parameter of ADMIN_MOVE TABLE? If I use AMT in Db2 11.5 to move an old table that was originally created in, say, Db2 9.5, it would be helpful for CREATE_TIME to be updated so I know that the table is new and no longer has any legacy structural issues to resolve.