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 BLU CDE tables only have the RECLAIM EXTENTS option of REORG enabled. This does not physically move rows and therefore REORG cannot reclaim extents unless 100% of the rows in an extent have been deleted (via deletes or BLU updates). Also...
The reorg online process need to lock the table in order to conclude. This is not a problem when you dont have many transactions, but when you have a 24x7 intense workload you might have a huge impact on your application.
Recommend/evaluate indexes – more information for each index
This is a point for tuning with indexes -> Tuning with indexes is still very common and useful. While using recommend and evaluate indexes it is possible to investigate each recommended index by updating USE_INDEX column in the table ADVISE_IND...
Increase the maximum size of a LOB object per table or per table partition
SQL and XML limits https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0001029.html
The maximum size of a LOB object of 4 terrabyte leads to the necessity of partitioning the table just due to this limit. S...
Pain point: Index rebuild stops if user terminates the connection accessing the table with an index that is marked inconsistent and it starts over from the beginning again on next table access by another user. Scenario:An index object is marked in...
Increase the number of ALTER TABLE operations that can be performed online without placing the table in "reorg pending" state
There are a few operations that seem to place the table into "reorg pending" state immediately when it should be possible to treat them as REORG-recommended. For example, any ALTER COLUMN .. DROP COLUMN statement that doesn't affect indexes should...
Remove The Need To REORG A Table Up On Performing Table Alter/REORG Recommended Operations
Today when we perform certain operations aka REORG recommended operations against a table like adding columns, dropping columns, changing datatype of a column, altering NULLABILITY of a column etc. the table will be put in a state called REORG pen...
æˆ‘ä»¬å¸Œæœ›ç»™ç´¢å¼•æ·»åŠ ä¸€ä¸ªå±žæ€§visible on/offæ¯”å¦‚ï¼šALTER INDEX VISIBLE ON ï¼ˆé»˜è®¤å±žæ€§ï¼‰ALTER INDEX VISIBLE OFF ï¼ˆç´¢å¼•ä¸å¯è§ï¼‰å½“ç´¢å¼•ä¸å¯è§ä»¥åŽä¼˜åŒ–å™¨æ— æ³•ä½¿ç”¨ä¸å¯è§çš„ç´¢å¼•ï¼Œå¦‚æžœéœ€è¦ï¼Œç›´æŽ¥alter index ...
Do not place IBM confidential, company confidential, or personal information into any field.