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:

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:

Status Future consideration
Workspace Db2
Created by Guest
Created on Apr 20, 2021

Full support for aggregate function with DISTINCT in OLAP SPECIFICATION

Use of DISTINCT with e.g. COUNT function in OLAP specification (PARTITION BY clause) returns error SQL0441N (SQLCODE -441).

Due to the fact that Db2 does NOT support the use of DISTINCT option in such cases, we have a major impact with COGNOS generated reports.

COGNOS would like to use the DISTINCT option, but is aware that Db2 doesn't support this, thus the Db2 adapted SQL avoids the DISTINCT option, but instead retrieves the whole data and performs the distinct and count and much more locally, which could be done much more efficiently by the database server. This causes dramatic overhead in network traffic as well as memory and CPU consumption!

For the 'COUNT DISTINCT' there's a pre GA option to enable that using undocumented environment variable DB2_COUNT_DISTINCT_SCALAG but this is not a general available solution and thus won't be sufficient to let COGNOS change the way to generate those reports.

And the requested DISTINCT support is not only needed for COUNT, but as well for AVG and SUM functions.

Needed by Date Jul 1, 2021