how to figure out load copy image file name or path location from log files in elegant way

Harishkumar .Pathangay

how to figure out load copy image file name or path location from log files in elegant way

hi,

this is a question for learning.

I have a backup image with 100 log files to roll forward. there is no source database. I do not want to restore and then get into a situation where LOAD is getting replayed and I am searching for a load copy image. I just want to make sure I have all the load copy images before even I start restore/roll forward. the only way to figure this from log files is using strings -utility in Linux. it gives the required information, by looking through 100 log files.

I am just looking for a elegant approach rather than using text search on a unreadable file.

db2fmtlog and db2logscan utilities do provide lot of information on log files and its contents, but not yet revealing the load copy image information from the log file.

Please let me know of any other good method for doing this. 

thanks,

harish pathangay

Roland Schock

RE: how to figure out load copy image file name or path location from log files in elegant way
(in response to Harishkumar .Pathangay)

Hi Harish,

my intuitive answer would be "Check the backup history file". But if you just have the starting base backup and all the transaction logs, you don't have a current backup history either.

As learned from Dale McInnis in one of his IDUG sessions, LOAD copies are always and only loaded from the location, they were stored to. So oppposite to logfiles, which can be retrieved ahead from e.g. TSM before rolling forward (which is ways faster!), load copies are always read directly. Otherwise, on a busy tape system, Db2 could request a log file and while it is processed, another system could require the just used tape to rewind and eject for another request, rendering your rollforward speed to a long wait.

This is the reason, why best practice says, put your load copies on a shared drive, reachable from both sides of HADR.

Cheers

Roland

Harishkumar .Pathangay

how to figure out load copy image file name or path location from log files in elegant way
(in response to Roland Schock)
Thanks for your valuable insights. I kind of understand that backup age and
load copy image go together. I was just looking for a fool proof way
considering the new utilities may help me. But still they did not. To err
is human. Thanks.

On Mon 7 May, 2018, 10:52 Roland Schock, <[login to unmask email]> wrote:

> Hi Harish,
>
> my intuitive answer would be "Check the backup history file". But if you
> just have the starting base backup and all the transaction logs, you don't
> have a current backup history either.
>
> As learned from Dale McInnis in one of his IDUG sessions, LOAD copies are
> always and only loaded from the location, they were stored to. So oppposite
> to logfiles, which can be retrieved ahead from e.g. TSM before rolling
> forward (which is ways faster!), load copies are always read directly.
> Otherwise, on a busy tape system, Db2 could request a log file and while it
> is processed, another system could require the just used tape to rewind and
> eject for another request, rendering your rollforward speed to a long wait.
>
> This is the reason, why best practice says, put your load copies on a
> shared drive, reachable from both sides of HADR.
>
> Cheers
>
> Roland
>
> -----End Original Message-----
>