RSSD Log Device Full

The Replication Server System Database (RSSD) log space has fallen critically low.

Symptom

These messages are reported in the Replication Server error log:

E. 2006/06/13 10:35:15. ERROR #11061 USER(western_dbo)
- s/stscol.c(1717) Check the log for error messages from
RSSD.
I. 2006/06/13 10:35:15. Message from server: Message:
7412, State: 1, Severity: 10 - - ‘Space available in the
log segment has fallen critically low in database
‘rssd’. 
All future modifications to this database will be
suspended until the log is successfully dumped and space
becomes available.’.
I. 2006/06/13 10:35:15. Message from server: Message:
7415, State: 1, Severity: 10 - - ‘The transaction log
in database rssd is almost full.
Your transaction is being suspended until space is made
available in the log.’.

Explanation

During subscription validation, the RSSD ran out of log space even though the truncate on checkpoint option was set. Replication Server halted and Adaptive Server suspended modifying all transactions. After you resolved the log space issue, Replication Server continued to process the subscription but did not validate it correctly.

Solution

Reduce the size of the log by dumping or truncating it:

Manually dump the log using these commands in the RSSD:

> sp_helpdb RSSD
 > go
 > dump tran RSSD to ...
 > go
 > sp_helpdb RSSD
 > go

If this step fails, truncate the log by executing dump tran with the truncate_only or no_log option.

To prevent this error, monitor the RSSD log. If the RSSD log becomes more than 80% full:

Suspend the operating system process that creates replicated objects (subscriptions).
Wait one minute to allow Replication Server to finish its transactions.
Dump the transaction log.
Resume the process.