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
Created by Guest
Created on Jan 14, 2015

Redesign of cleanup on remote cursor load of LOB data

Customer migrated from DB2 9.1 on Solaris to DB2 9.7 on
Linux. As restore is not supported between different endian
architecture, load by remote cursor was used for data
movement. There was one single table storing about 400 GB of
LOB data (BLOB), total size of database was about 500 GB. The
remote cursor load of LOB data exploits the temp tablespace by
creating temporary files and runs cleanup only at the end of
load. This leads to disk full condition as the temporary files used
1.5 TB which was the size of the underlying filesystem.
PMR was opened, conclusion was that the design of the load
needs a cleanup of the temporary files at the end of the whole
table. It is not currently possible to periodically cleanup the
temporary files, this desgin change is required to avoid the disk
full condition.