Hi Rick,

When a full backup occurs, the previous log and differentials
are "inactivated", not "invalidated".
i.e. they are changed from "active" to "inactive".

You should be able to use the GUI to select FULL backup from the 6th,
and then select all of the individual log backups that you want to
restore (active and inactive)... and restore them that way.
If the "auto-select" gets in your way, you can do them a few at a time,
Make sure to only check the "Recovery" checkbox on the LAST log restore.

The problem you might run into is if there was some database reorg
or defrag or something else that might cause the log backups
that were intended to be applied to the 7th, 8th, or 9th full backups
not to apply correctly to the backup from the 6th.

If you are having trouble, you should call IBM support to have
them walk you through this.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/12/2008
12:04:17 PM:

> [image removed]
>
> Re: Retrieving invalidated SQL transaction logs
>
> Rick Saylor
>
> to:
>
> ADSM-L
>
> 05/12/2008 11:40 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Del,
>
> Thanks for the quick response, but I'm actually referring to the logs
> that get invalidated when a full backup occurs. What my DBAs are
> trying to do, since the full backups on the 7th, 8th an 9th are no
> good, is get all of the logs after the May 6th backup. However, these
> logs are marked as inactive on the GUI but we don't see them when
> using the command line. The hope is to restore the May 6th backup and
> apply all the inactive logs to the database.
>
> Thanks,
> Rick
>