DB2 ROLLFORWARD ERROR when doing "TO A POINT IN TIME" option I do restore command of backup image which was made 03.03.2015 at 19:20:

db2 restore database maxdb71 from "/data/archiveBackup" taken at 20150303192002 without prompting;


Then I try to do the rollforward to a point in time (03.03.2015 at 21:05) so this is after the backup image:

db2 rollforward db maxdb71 to 2015-03-03-21.05.00.000000 using local time and complete;


But I receive error:

SQL4970N  Roll-forward recovery on database "MAXDB71" cannot reach the 
specified stop point (end-of-log or point-in-time) on database partition(s) 
"0". Roll-forward recovery processing has halted on log file "S0000189.LOG".


So like it cannot find log  S0000189.LOG.
But this log EXISTS in the archive log location (C0000004 currently subfolder is used for archive logs) /data/archive/ctginst1/MAXDB71/NODE0000/C0000004&gt;:

these are the timestamps for some of archive log files:

ctginst1 db2iadm1 15765504 2015-03-03 19:22 S0000187.LOG
ctginst1 db2iadm1 16785408 2015-03-03 21:52 S0000188.LOG
ctginst1 db2iadm1 16785408 2015-03-04 00:15 S0000189.LOG
ctginst1 db2iadm1 16785408 2015-03-04 02:32 S0000190.LOG


Basically log file S0000188.LOG should be the one which contains transactions from 21.05, right?

So why I cannot do the rollforward of point in time when I have necessary logs?
I am really confused with this rollforward option.

When I do db2 rollforward database maxdb71 to end of logs and complete;
it is successful and I get information:

 Log files processed                    = S0000187.LOG - S0000188.LOG


So to end of logs works but why I cannot perform until some specific point in time?
If you archive logs to a location different from the active log directory (logpath database configuration parameter), you need to specify the clause overflow log path /path/to/archived/logs. The ROLLFORWARD command does not do it automatically.

PS. You really should start reading manuals -- they are full of useful stuff, including multiple examples...