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 Submitted
Created by Guest
Created on Oct 24, 2024

Avoid potential data loss in time intervals containing PIT ranges

If you want to create REDO SQL for a time interval, and there is a PIT range somewhere in this interval, Log Analysis Tool (LAT) will print this informational message ""ALAA156I: LOG RECS BYPASSED DUE TO PIT RECOVERY". The job will end with "RC=0000".

If you do not see this message, you do not know that LAT has bypassed some records and that you did not get all the records you were looking for.

Example: You take an images copy of at tablespace at 01:00. At 10:00 you did a PIT recovery of the tablespace, back to 06:00. Now, at 11:00 you regret this and want to get the tablespace back to 09:59, right before the recover job started. The Db2 recover utility will not let you do another PIT recover back to 09:59. You must recover to the imagecopy at 01:00 and then use LAT to create REDO SQL from 01:00 to 09:59. But the recover running at 10:00 marked at PIT range in SYSIBM.SYSCOPY for this tablespace from 06:00 to 10:00. When running LAT with default options, we get the message "ALAA156I" and LAT is now bypassing all records in the Db2 log, from 06:00 to 09:59. If you do not see this, you could have a potential data loss.

The current solution is to have the user manually checking for a PIT range for the involved tablespaces. Or, to detect ALAA156I messages. Then the user can specify option "P" in "Misc flags" regarding "Include partial recovery points" and LAT will now include records from 06:00 to 09:59 in the example above.

I would like to introduce a new value for option "Misc flags". Lets call this option "S" meaning: "Skip partial recovery points". Then I want LAT to check SYSIBM.SYSCOPY for PIT ranges for the tablespaces involved, overlapping the time range specified to LAT, and at the START of processing a request. If a PIT range is present at the time interval specified to LAT, and the user of LAT had not specified "P" for Include or "S" for Skip, I want LAT to stop immediately with "RC=0008". 

Please be aware: I do certainly not want LAT to run for days, processing TB's of Db2 logs and then ending with "RC=0008" because of this new functionality. This check for PIT ranges must be performed at start of processing.

 

Needed By Quarter