Manually draining the RSSD transaction log

If Replication Server has routes to other Replication Servers, make sure that Replication Server processes all transactions in the RSSD transaction log before you upgrade the databases.

You can make sure the transaction log is completely processed by creating a replication definition in the primary Replication Server and then watching for it to appear in the replicate Replication Server RSSD. When the replication definition is in the replicate RSSD, the log is fully processed.

1. Log in to the primary Replication Server.

2. Create a temporary replication definition:

   create replication definition rep_def_name 
      with primary at dataserver.database 
      (column_a int) 
      primary key (column_a)
   

3. Log in to the replicate RSSD.

4. See whether the replication definition has arrived from the primary RSSD:

   select * from rs_objects 
      where objname = "rep_def_name"
   

When the replication definition has arrived in the replicate RSSD, the RSSD transaction log has been drained.