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: 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


Status Not under consideration
Workspace Db2
Components pureScale
Created by Guest
Created on Apr 19, 2015

SQLTIMEOUT during FileNet CM metadata creation operations

A SQL_TIMEOUT is experienced when executing multiple SQL statements in a pureScale environment. This does not happen in a non-pureScale environment and when pureScale is configured with only 1 active node. The PMR mentioned has a multitude of data and description of the core problem.
  • Guest
    May 30, 2019

    Looking at the old PMR, it seems like the problem stemmed from the application not committing enough.  It is unclear what is the ask for the feature request.  Having said that, the product version when this was reported was V10.1 stream.  We have since released several major releases and modpack.  I would suggest this the same application to run against the latest version.  If this remains to be a problem, engage Db2 support with the new set of data to investigate where is the bottleneck.  The feature request system is not to be used for investigation.  Returning this one for now.