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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


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