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 Delivered
Created by Guest
Created on Dec 17, 2019

Allow REPAIR CATALOG on indexes to reset version numbers

Allow REPAIR CATALOG on indexes to reset version numbers

In Db2 Cloning Tool, index version mismatches cause indexes to be rebuilt on the target rather than using the physical copy. Some of these indexes are very large. Corrective measures would be to drop and recreate the index on the source which would not be possible. If the version number could be set to a value matching the source in a non-invasive fashion this would alleviate the long duration of these index rebuilds. In Db2 today, this is possible for tablespaces which will repair the catalog version numbers to a value matching the underlying page set.

Rebuild Index is a huge resource hog on the z/Machines. 

All 5 Customers Systems  and 6 DBAs that manage it at Duke Energy using the IBM Cloning tool for Db2 on z/OS are impacted. 

Needed by Date Jan 31, 2020
  • Admin
    May Chu
    Apr 3, 2020

    The requested capability already exists. REPAIR CATALOG supports indexes and will correct version information in indexes. It does not perform schema validation however. If this requirement is for Cloning Tool to exploit REPAIR CATALOG then a requirement should be entered against the Cloning Tool product.