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