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
Workspace Db2
Components Serviceability
Created by Guest
Created on Feb 11, 2015

SQL0659N message should identify object and limit reached(RIMS)

'SQL0659N Maximum size of a table reached' In above message SQL0659N the customer would like the object identified with it's name or Object ID and Tablespace ID as well a what was the limit reached (64GB, 256GB...). This is in order to identify the object accurately and to know what exact limit was reached. In the customer's PMR the SQL0659N message was returned from the load command but it was not the table being loaded that was encountering the limitation but a temporary table created by the cursor that was opened to read from. It was a load from cursor where the cursor was associated to a complex query requiring lots of tempspace. If the SQL0659N message would have identified the temporary table it would have enabled the customer to fix the problem by himself.