DB2 Rollforward with an overflow log path.

Body

This one is a fairly simple one, but the question has come up a few times this week already.  When you are using an overflow log path in your ROLLFORWARD command and you are doing it in stages you need to include that overflow log path in your final STOP command as well (so DB2 can find those logs for the final wrap up of the rollforward.  If you leave off the overflow log path on the final "stop" or "complete" command you will get an SQL1273N error about missing logs.

A simple example of how to do it correctly:

db2 rollforward db sample to end of backup OVERFLOW LOG PATH (<path to the extracted logs>)
    Now that you have ensured that the rollforward was successful (no errors) and you want to complete it and bring the database to a connectable state
db2 rollforward db sample stop OVERFLOW LOG PATH (<path to the extracted logs>)

*****

Thanks for reading.

Andy