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.
The option ordinality is used in XML queries but the overall performance is very slow
We use the for ordinality option in our queries but the over all performance is very poor.There is a specific XSCAN needed when ordinality is specified which takes a long time. this XSCAN produces a sequence of XML ELEMENTS. This sequence is then ...
Add option ：statement rollback is able to release the locks for the failed statement.
When -803 ( violating unique key constrain ) happen on a statement, there are two things happen1) db2 still hold the lock on the row accessed by the statement that cause -803 , no matter the statement had fail.2) The transaction was not rollbacked...
Support mixed row/column environments without requiring CUR_COMMIT=ON
We have recently run into a problem when we enable Cur_commit because of the locking behavior expected by some applications (they expect blocking). Therefore, we have to disable CC, but then that app cannot use blu. We want to give our plant the a...
To remove tablespace maintenance restrictions on pureScale
To remove all the restrictions of SQL1419N Reason code = "11" on pureScale. 11 Altering database containers is not supported in a DB2 pureScale environment. As a result, the following clauses are not supported with the ALTER TABLESPACE statement i...
Use FSCR information to ommit empty data pages while performing Table Scan (TBSCAN)
ABSTRACT:Table scan over volatile table with large number of empty pages scans all empty pages instead of using FSCR to find pages to be scanned. VERSION INFORMATION:DB2 9.7.FP5 on Linux / DB2 9.7.FP9a on AIX 7.1 / DB2 10.5.FP4 on Linux TECHNICAL ...
Allow converting of the SYSCATSPACE to the reclaimable storage.
There is no way to convert the Catalog tablespace to RECLAIMABLE storage. The only workaround is to create a new database and to migrate the objects and the data. Since, we have a lot of databases which were created in pre-9.7 versions, we are stu...
Be able to DROP "restore pending" TABLESPACES supporting RP tables after RESTORE REBUILD
After RESTORE REBUILD of a slice of Prod DB into Pre-Prod DB, it is impossible to drop "Restore Pending" tablespaces supporting RP tables, you get SQL0282N. You can't detach "unrestored" partitions into junk either SQL0290N. So you are stuck and t...
Do not place IBM confidential, company confidential, or personal information into any field.