Peter Sands wrote:
Hi,
I am right in assuming to recover a database where logretain is on.
That I only need the logs that are reported in the list history.. for
instance;
db2 list history backup since 20040228190050 for db trdb
reports that the earliest log is:S0000012.LOG and the current log is:
S0000012.LOG
I only need that S0000012.LOG log to recover in a roll-forward
situation, plus the datbasebase dump.
Or can I just get the required log using..
db2 get db cfg for trdb | grep "First"
First active log file =
S0000012.LOG
Which returns the same log number.
thanks
PS
You only need the logs if you have created an
online backup. Offline backups can be restored
without rolling forward thru the logs.
For online backups you need the logs that have been
produced from the beginning of the backup to the end.
That means you always have to rollforward the database
to at least the log that has been active at the end of
the backup.
In DB2 V8.1x the current log gets automatically
closed at the end of an online backup to ensure that a complete
set of logs is available for recovering from this backup.
In Version 7.2x you might need to manually issue the
db2 command 'archive log for db <dbname>' at the end
of an online backup to ensure that all logs are available for
recovering.
In your case there have not been much activity on
the database during the backup, so log S0000012.LOG
seems to be enough to rollforward your database.
Best regards
Eric
--
IT-Consulting Herber
***********************************************
Download the IFMX Database-Monitor for free at:
http://www.herber-consulting.de/BusyBee
***********************************************