Hi. I'm trying to clone a database across servers. No matter how I attempt it end up with a db in "roll forward pending state" but I can't roll it forward due to error SQL1265N - The archive log file "S#######.LOG" is not associated with the current log sequence for database "$DB_NAME" on node "#".

I'm using the following commant to back up my db:
And restore it with the following:
That runs fine. But then I end up with a db that I can't connect to until it rolls forward to the end of logs. And it claims no association to the logs I have. I thought using include logs would make sure it grabbed the right ones, but it doesn't appear to have fixed anything.

For what it's worth, heres the query status:
Any help will be appreciated. Thanks.

use the following command:

db2 "rollforward database $DB_NAME to end of logs and stop overflow log path (/home/db2inst1/logs/) noretrieve"

Thanks for the quick response. No luck though.

Please make sure that there are no logs in the active log dir. Move them somewhere else if you see any.

I'm not totally sure what the active log dir is (I'm a db2 noob in case you couldn't tell). I removed the logs from /home/db2inst1/logs/ and tried your command with noretrieve. It still gave me SQL1265N.

Explanation:
For roll-forward recovery, the log files need to be processed in
correct sequence. The log file sequence is determined by the
database that has been restored or the log files that have been
processed. In addition to this, for table space level
roll-forward recovery, the log files must be processed in the
sequence through which the current state of the database has been
reached. The specified archive log file was found in the log
directory or the overflow log path for the database on the
specified node but the log file is not in the correct log
sequence.
Roll-forward recovery processing stops.
(Note : if you are using a partitioned database server, the node
number indicates which node the error occurred on. Otherwise, it
is not pertinent and should be ignored.)
User Response:
To determine the correct archive log file, issue the ROLLFORWARD
DATABASE command with the QUERY STATUS option. Move the correct
archive log file into the database log directory or, if the
database is in a consistent state, change the log path to point
to the correct archive file and issue the ROLLFORWARD DATABASE
command again. Alternatively, resubmit the command with the
overflow log path pointing to the correct archive file.

execute "db2 get db cfg for <db name> | grep -i path", go to the dir pointed to by "Path to log files" or "Changed path to log files" and check if there are any log files. If you find any, move the somewhere else. Then, put the onces you extracted from the backup image back to /home/db2inst1/logs and redo the rollforward.

That appears to have worked. I am in your debt.

I don't even have a log folder, am I missing something?

Please be more specific.

I don't even have a log folder, am I missing something?

is this related to the same system/problem
otherwise : do not mix different problems in the same entry ..