Draining the RSSD Transaction Log

Create a replication definition to manually drain the RSSD transaction log. This ensures that Replication Server processes all transactions in the RSSD log before you upgrade databases if Replication Server has routes to other Replication Servers.

To make sure the transaction log is completely processed, create a replication definition in the primary Replication Server and verify that it appears in the replicate Replication Server RSSD. When the replication definition is in the replicate RSSD, the log is fully processed.

Log in to the primary Replication Server.
Create a temporary replication definition:
```
create replication definition rep_def_name
with primary at dataserver.database
with all tables named 'table_name'(column_name datatype)
primary key (column_name)
```
Provide the names for the data server, database, table, and column, and the datatype of the column. See the Replication Server Reference Manual for the complete syntax.
Log in to the replicate RSSD.
See whether the replication definition has arrived from the primary RSSD:
```
rs_helprep rep_def_name
```

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