hand-rollforward on a standby for windows

[Juan Norton]

Got DB2 v8.2 WUE
-Machine A runnig XP
-Machine B " 2003 server

I have the following error trying to do a hand rollforward on machice
B:

db2 => rollforward database BD to end of logs
SQL1265N The archive log file "S0018161.LOG" is not as
current log sequence for database "BD" on node "0".

What I want to have is a standby database of A's bd on B so minimize
out of service time. What I did is:

-Make a full online backup including logs of A's bd and send it to B.
-Restore the backup image on B.
-Rollforward it to end of logs but not complete.
-On A did a archive log command.
-did a get db cfg so I saw which logs file were archived so pass them
to B.
-Send the archived files to B.
-Did I rollforward to end of logs in B, showing me the error above.

I know HADR is a nice solution but we do not have any budget. I tryed
using user exit programs but found to many error and problems.

Appreciate any help.

Juan

[Steve Pearson (news only)]

% db2 "? sql1265n"

SQL1265N The archive log file "<name>" is not associated with
the current log sequence for database "<name>" on node
"<node-number>".

Explanation:
[...]

-------------------------------

Basically, DB2 doesn't believe that the log file mentioned in the error
message belongs with the current log stream (aka log chain) of the
database.

DB2 tracks unique log chains to prevent different versions of a
database's history from intermingling. A new log chain is defined at
any log truncation event. This occurs for such operations as:
- online backup
- rollforward to point in time
- explicit archive log file command
- (maybe others)

So my guess is that the ARCHIVE LOG command that you're doing is
causing a log truncation (and new log chain) that the standby doesn't
like. Can you consider not forceing the logs to archive, and just
waiting for them to archive naturally when they fill up? That would
avoid this issue.

Regards,
- Steve P.
IBM DB2 UDB for LUW Development
Portland, OR