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,
Post an idea
Upvote ideas that matter most to you
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.
Currently whenever we create an index on a table we see significant number of lock timeouts for the applications. We are running a pureScale cluster and not able to create Indexes ONLINE.
We use DB2 LUW pureScale as a customer facing environment, every time we create an index there will be an interruption to the services due to the S lock which is incompatible with concurrent writes from other applications. For us this is unacceptable as we don't have any work around.
Our non-customer facing environments use MS SQL server and they support ONLINE Index creation in a couple of modes, ONLINE mode and ONLINE RESTARTABLE mode. We are losing the argument to Microsoft SQL server and even postgreSQL (open source) supports ONLINE Index creation when you specify CONCURRENTLY option. We need this option in DB2 LUW as soon as possible as in this AGILE/Devops age creating indexes and deploying services on the fly is becoming more and more common.
We don't mind if the locking needed to create index is at a couple of points like MS SQL server does, when it initially starts the index and when it completes the index but they are for very short duration.
Our services are getting locked out for the most part of the index creation on DB2 LUW tables especially when they are large. DB2 LUW is getting a bad rap because of this and losing its competitive edge.
Do not place IBM confidential, company confidential, or personal information into any field.