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 Future consideration
Workspace Db2 for z/OS
Created by Guest
Created on Jan 8, 2017

Enable customers running 24/7 to create unique indexes

Our Internet and Mobile applications are used 24/7 and we do not have any batch windows nor any maintenance windows.

When creating new indexes on existing tables the a CREATE INDEX operation generates an unwanted outage when created with DEFER NO.

To avoid the outage you would like to use DEFER YES which defers the index build until a REBUILD INDEX utility execution. This works perfectly well for an index that is not defined as UNIQUE. For a UNIQUE index it is put into Rebuild Pending status which in turn means that the data cannot be read or updated with SQL until the index is rebuilt. An SQLCODE-904 will be returned to applications trying to access the table independent on access path.
  • Guest
    Feb 14, 2020

    I have recommended to make new (or changed) indexes NOT UNIQUE as far as possible, when some other existing index enforces and required uniqueness. 


    Michael Hannan