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:

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 Future consideration
Workspace Db2
Created by Guest
Created on Oct 27, 2017

Decouple archive log purging from BACKUP utility

For databases using AUTO_DEL_REC_OBJ, at the end of the BACKUP utility there is a synchronous process which purges any history records and their associated archive logs. This can take a very long time on busy systems. It is necessary to decouple this purge process so that it is either optional (perhaps an extra option on the BACKUP command) or by making the purging asynchronous.
  • Guest
    Apr 11, 2019

    This was prompted by a situation, driven by GDPR requirements, where very larget amounts of updates / deletes were being carried out.   Because of the number of archive logs being pruned after AUTO_DEL_REC_OBJ came into play, it was found that a backup taking about 3 hours was followed by a 24 hour history file cleanup / log purging exercise.


    The time it takes is directly related to the number of items in the history file, rather than the size of individual log files.   However, increasing log file size by too much adds extra exposures (logs not being archived "off box" quickly enough.