Environment: DB2 V9.7 FP 3a, Multipartitioned environment with 17 partitions spanning across 3 physical nodes
Operating System: Linux
Backup failed with SQL02428N.
We have an online backup with include logs. I see a strange situation here.Backup has failed complaining that it couldn't retrieve a logfile. But the strange thing is that the logfile which it is complaining was already archived 12 hours before the backup started.
Take the example for NODE 1 in the below scenario. The log file would be S0016416.LOG. Notice the timestamps
Logs are archived as they become full; they can remain active until transactions stop using them. So, S0016416.LOG became full and was archived at 2011-07-12-220.127.116.114404, although the transaction that had been using it remained active until at least 2011-07-13-01.37.46.101342.
@n_i, I guess the transaction using log 16416 was active at 2011-07-13-00.18.15 but was committed/rolled back before 2011-07-13-01.37.46.101342. If the transaction had been active at 1.37.46, the log would have been available in the active log directory.
Visit the new-look IDUG Website , register to gain access to the excellent content.