Usually our Db2 backs up to storage server or natively. Occasionally we restore a Db2 system in another operating center from where we have to access to the storage server for Restore/rollforward.
In the target environment the Db2 archive logs are extracted via db2adutl afterwards transferred to the destination directory and finally rollforward and similarly with native transfers.
At this moment we have only db2cklog utility which checks the integrity or validation of archive log however does not give information when this archive log was generated and to which database this archive log originally belongs to.
So situation becomes complex where we have to do multiple crossnode restore, rollforward operations.
It becomes cumbersome when we are dealing multiple DPF databases as well
|Who would benefit from this IDEA?||All customers who do crossnode recovery and need archive logs information for rollforward operation|
How should it work?
1) db2cklog utility should tell us the source of archive log, i mean what is the DB NAME from which this archive is generated
db2cklog utility should tell us the timestamp of archive log or generation time.
2) The measurable benefit would help us in consolidated db2 environments
3) The current workaround today is to go on source db2 server and run db2 list archive log history all or check the db2diag.log from source side which is time taking procedure.
|Priority Justification||It is much need feature in consolidated and DEVOPS environment|
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions