Hi Bobby,
thanks again for your response.
Here is an example where rollforward in my opinion has some limitations:
1. You have created a user at 14:05 in the database.
2. You do a restore (Data Volume + DB Instance FS (Log Header File)
3. You do a PIT to 14:03, with log files 0-10 from Chain 0 (Chain 0 contains Log 0 - 15)
4. The db is started and it creates a new log 10 in Chain 1 (transactional work is done and Logs 10 - 13 are created)
Now you decide to go back to 14:05 when the user was created. This will not work because rollforward will use the log 10 from chain 1 and not from chain 0. So you will not be able to reach this point.
If you rename / move the chain 1 to something else (so the db is not able to find the latest log 10) , the database will colllect log 10 from chain 0 (and maybe further neeeded logs) , you will be able to reach the point the user was created.
Another option would be to use rollforward with noretrieve and copy the needed log files manually from chain 0.
DB2 recover which is using the history file can handle this without any problem, no user intervention is required.
I know maybe this example is a bit strange... but in may opinion this should be possible. Rollforward is much more comblicated in my opinion.
Best Regards,
Andreas