Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 Dec 2, 2024

Rollforward should proactively determine if END OF LOGS will not be able to be reached

  • In a partitioned database environment, if there is some log file from a database partition that is missing, the database can only be recovered to a point in time where the log files from all database partitions are available. If only the log files from the log archive are available, then you cannot use END OF LOGS as the stop time for a rollforward operation. This is because unarchived log files from the active log path are not available, and the rollforward utility processes only available log files. Using END OF LOGS in this situation can result in some database partitions having data that is inconsistent with other database partitions, and resulting in error SQL4973N.

  • Rollforward utility should be smarter, it would be better if it automatically detected and figured out where the end is that is reachable proactively and disallow END OF LOGS option if it cannot reach that end.


Needed By Quarter
  • Guest
    Jan 15, 2025

    It is a current product limitation, that ROLLFORWARD utility relies on user to determine the intended recovery (either END OF LOGS or point-in-time) can be performed, ie. there are sufficient log files (on all database partitions in DPF) to reach the specified recovery target.


    It is often overlooked, so the ROLLFORWARD command was issued, and then failed because some logs from a particular database partition is missing or damaged. Once in that situation, and the log file cannot be recovered, user is forced to repeat the recovery to an earlier time. This is very expensive (requires restoring the database again, so can take a long time).


    The ask is for the ROLLFORWARD utility to detect missing or damaged log file prior to replaying the good log files. While possible, the development cost is going to be high.


    There was previously a plan to provide a tool, to help determine what is a safe recovery target point to use, prior to running ROLLFORWARD. This can be viewed as a cheaper solution to this feature request.


    We will have to prioritize this against many other feature requests. It is not clear this is going to be ranked high.