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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


ADD A NEW IDEA

FILTER BY CATEGORY

Db2

Showing 1046
100 VOTE

Support of RUNSTATS of range-partitioned tables on single partition

RUNSTATS on range-partitioned tables always runs on allpartitions. If all indexes are partitioned, a RUNSTATS of a singlePartition would be helpful.
almost 7 years ago in Db2 / Utilities (Export, Import, Load, db2look, etc) 0 Future consideration

Automatic Lock-Escalation from Row- to Extent-Level

Db2 is mainly using row-level locking and tries to avoid lock-escalation to table-level. This behavior is helpful in most of Db2s use cases, but there are some particular situations when locking on a higher level than row would be beneficial. Cons...
8 months ago in Db2 / Other/Unknown 0 Future consideration

Online index reorg for pureScale

Currently online index reorganization is not supported in Db2 pureScale environments and will fail with SQL1419N.
almost 2 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) / pureScale 2 Not under consideration

Poor performance on DB2 V11.1 due to changes in build process

Some customers are noticing performance degradations moving from v105 ESE to v111 ESE on the same hardware.These degradations are most pronounced in OLTP workloads, with an emphasis on INSERT and UPDATE operations.Db2 Support has confirmed that th...
over 2 years ago in Db2 / Serviceability 0 Not under consideration

Allow CREATE/REPLACE for users other than owner

Currently on Db2 LUW CREATE OR REPLACE is only allowed for the owner of a database object. CREATE OR REPLACE authorization should be opened up to allow create/replace by anyone who has the ability to drop the object and to create the object with a...
about 3 years ago in Db2 / Statements (DDL and DML) 1 Not under consideration

Online BAR from pureScale to non-purescale

There are many cases that a database on the purescale cluster is needed to move on non-purescale instance. for example,backup, development or DR system . However, oracle does support this.
about 2 years ago in Db2 / pureScale 0 Not under consideration

Decouple archive log purging from BACKUP utility

For databases using AUTO_DEL_REC_OBJ, at the end of the BACKUP utility there is a synchronous process which purges any history records and their associated archive logs. This can take a very long time on busy systems. It is necessary to decoupl...
almost 4 years ago in Db2 / Backup, Restore, Rollforward, Recover 1 Future consideration

Improve performance of SET INTEGRITY command through use of (intra partition) parallelism

SET INTEGRITY does currently not make use of intrapartition parallelism.SET INTEGRITY (with "checked" option) for large tables and/or tables with many foreign key and/or check constraints consumes a large amount of time while the table is not acce...
over 1 year ago in Db2 / Serviceability 0 Delivered

Enable classic reorg with "allow write access"

Many customers want to REORG their tables quickly and efficiently. The classic REORG is by far the fastest option but puts the table in read only mode. Inplace reorg allows write access but is much slower and not suitable for tables that have a hi...
over 4 years ago in Db2 / Utilities (Export, Import, Load, db2look, etc) 3 Future consideration

Table partitioning for column-organized tables

Column-organized tables are currently not supported for table partitioning (e.g. PARTITION BY RANGE)..At the same time, table partitioning is used by many data warehouse customers to speed up ETL activities - e.g.:(a) load new data into a separate...
over 4 years ago in Db2 / BLU Acceleration 0 Future consideration