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.
Create INDEX and SKPT lock. DDL and continuous availability.
Working in a banking 24x7 environment without any maintenance window our concurrency issues with DDL changes are increasing more and more everyday as our workload increases.
There are some concurrency problems that we think it should value the effort to review in order to relieve the situation by modifying the locking strategy DB2 is taking. One of our issues occurs when creating a new INDEX in an application core DB2 TABLE, we do not reach to understand why a CREATE non UNIQUE INDEX DEFER YES is in need to acquire an exclusive SKPT lock at the beginning of the process over all the packages associated with the DB2 TABLE.
Why does DB2 need this lock? this occurs in a CREATE non UNIQUE INDEX with DEFER YES, the index is new, so it is not in use; for our understanding there should be no need to acquire this lock at all, and by avoiding this lock the index creation process would have ended successfully after a REBUILD SHRLEVEL CHANGE without any online concurrency issues.
Do not place IBM confidential, company confidential, or personal information into any field.