Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

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

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

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.