Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

BLU Acceleration

Showing 6

Allow EBCDIC collation for column organize tables

Db2 does not support anh collation other than IDENTITY or IDENTITY_16BIT per this link - https://www.ibm.com/docs/en/db2/11.5?topic=to-restrictions-limitations-unsupported-database-configurations-column-organized-tables. Customers who are wanting ...
about 1 year ago in Db2 / BLU Acceleration 0 Future consideration

Db2 TOTAL_CPU_TIME monitoring metric on AIX should reflect "wall" CPU time and not use PURR-scaled time reported currently by thread_cputime AIX API

Db2 monitoring interfaces report "CPU time" metric (TOTAL_CPU_TIME), which accounts the time that given activity/request (and all higher level aggregated interfaces) spent actively "on CPU" whilst executing the query. On AIX this information is ob...
about 1 year ago in Db2 / BLU Acceleration 0 Future consideration

Rebuild BLU columnar dictionaries and recompress data in BLU columnar tables

An engineered capability is required to automatically rebuild an optimal BLU columnar compression dictionary and recompress BLU columnar tables. A technique is needed to easily rebuild and recompress columnar tables like we have for adaptive compr...
over 1 year ago in Db2 / BLU Acceleration 0 Future consideration

Add REORG LONGLOBDATA for columnar tables

Currently we can create columnar tables with CLOB/LOB columns in it. What we can't do is reclaim the allocated diskspace of the CLOB/LOB columns (LOB_OBJECT_P_SIZE) in columnar tables To get an idea about how many diskspace is allocated: db2 "...
about 2 years ago in Db2 / BLU Acceleration 0 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 7 years ago in Db2 / BLU Acceleration 0 Future consideration

BLU CDE Online REORG

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...
almost 9 years ago in Db2 / BLU Acceleration / Tables/Index (Range MQ MDC etc.) 5 Future consideration