Archiving the transaction log

Before you archive any DB2 Universal Database transaction logs in a primary database, you must make sure that the Replication Agent has finished processing all replicated operations in the log using the following procedure.

To determine whether operations in the log have been processed by the Replication Agent

1. With the Replication Agent in Replicating state, use the ra_locator command to retrieve the current value of the LTM locator from the primary Replication Server.

   ra_locator update
   

   The current value of the LTM locator from the primary Replication Server contains the DB2 Universal Database log sequence number of the last transaction operation to be replicated successfully.

   Characters 4-19 of the origin queue ID are the 16-character (8-byte) operation sequence number. Characters 8-19 (6 bytes) of the operation sequence number are the DB2 log sequence number.

2. Use the DB2 db2flsn command, with the log sequence number identified in the origin queue ID, to identify which log file contains that log sequence number.

   You can archive any log files up to the log file name returned by the db2flsn command.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF