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 Nov 3, 2014

deferring index creation with an option to not have to log the rebuild

This was originally opened in Aug 2013 RIMS database (as 8556)

In Aug 2013 one of the ids-System customers, an insurance company, had to do an offline table reorg, which had to rebuild index at the

end. This is an HADR customer, so index is fully logged, except this runs into log full and index is marked bad. After this, any

access triggers rebuild, but always fails with log full. This repeats throughout the evening. The system was set up years ago, with

an active log configuration that would be big enough for the table / index size. But now things are much bigger. Not only the index

is much bigger now, but more significantly is the concurrent transactions during the time index was being rebuild. The rebuild is a

long operation, so all the transactions performed concurrently during the rebuild would require significantly more log space.

Extreme steps were taken (customer set logsecond to -1, change config so it is not fully logged, stopped HADR and reinitialized the

standby after wards) to get customer out of this situation. After this, they have increased active logs (so the largest index is now

1/4 of the total active log space). This will buy them some time, until table / index grows significantly again.

They are looking for improvements, in particular, they are asking for what z/OS has for deferring index creation with an option to not

have to log the rebuild, but generate a copy image for the index, much like load does.