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 Not under consideration
Created by Guest
Created on Dec 11, 2018

IDAA Loader disabling tables in IDAA upon failed load RFE 128179


IDAA-IDAA Loader product is disabling a table when the load fails for  
any reason, causing serious performance issues as queries will start running in DB2.  We need the tables to remain enabled when the LOADER fails.

Use Case
Once the table is disabled, even though the load completed  successfully the second time, the queries start going to DB2 vs the IDAA and they run very slowly causing a cascade of performance issues.   Leaving the table enabled will match the behavior we had prior to using LOADER (ACCEL_LOAD_TABLES) and eliminate our recurring performance issues.
  • Guest
    Jan 24, 2019

    This is a good idea.  We'd like to gauge customer interest in this idea to help prioritize its possible implementation.