Skip to Main Content
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
Created by Guest
Created on Jan 22, 2021

setup limitations on cpu, memory, workspace and elapstime

Hi, when migrating from Netezza to the new IDAA appliances (Db2 Blue), we saw a lot of new issues popping up. One major issue that is still not solved in v7.5.3, is that we experience a lot of very long running queries in the appliance. Sometimes > 200000 seconds. Probabely due to a lost connection or a bad closedown of the client. Nevertheless, the IDAA is sometimes hanging on these queries, probabely due to very high use of temp space. Cancelling this queries makes IDAA working again. Our contact personen in the IDAA Boeblingen lab, told us it is not planned to foresee an automatic cancel feature after certain limits of cpu, elaps, memory, sortspace, resultsize...

Needed by Date Jan 22, 2021