Skip to Main Content
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 Feb 2, 2015

Creation of range-partitioned tables during TRANSPORT

Whilst working on a recent pureScale POC with a customer, we came to the stage of upgrading their existing database to pureScale. Existing database had a catalog SMS tablespace.

pureScale has a requirement that all tablespaces have to be AUTOMATIC storage. Whilst we can convert DMS tablespaces during a redirected restore, there is no conversion functionality of SMS to DMS. Only way is to create an empty target db with automatic storage and use TRANSPORT functionality with redirected restore. However, TRANSPORT does not recreate range-partitioned tables. So, only way is to rebuild target db using db2move, which is far from ideal from 25x7 organisations.