DSI shuts down because replicate database log is full

Symptom

The DSI thread shuts down and the following error message is displayed in the Replication Server error log:

E. 2006/06/13 10:49:07. ERROR #1028 DSI EXEC(107(1) SYDNEY_DS.pubs2) -
dsiqmint.c( 2361) Message from server: Message: 1105, State 3, Severity 17
-- ‘Can’t allocate space for object ‘syslogs’ in database ‘pubs2’ because
the ‘logsegment’ segment is full. If you ran out of space in syslogs, dump
the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to
increase the size of the segment.
H. 2006/06/13 10:49:07. THREAD FATAL ERROR #5049 DSI EXEC(107(1)
SYDNEY_DS.pubs2) - dsiqmint.c(2368) The DSI thread for database
‘SYDNEY_DS.pubs2’ is being shutdown.
DSI received data server error #1105 which is mapped to STOP_REPLICATION.
See logged data server errors for more information. The data server error
was caused by output command #1 mapped from input command #1 of the failed
transaction.

Explanation

The DSI thread to the replicate data server has shut down because the Adaptive Server log for the database is full. A full Adaptive Server log could be caused by:

This problem is related to “Adaptive Server last-chance threshold passed”, which occurs when the Adaptive Server log for the database is almost full.

Solution

Complete the following tasks:

  1. Add space to the Adaptive Server log, after verifying that there is space in the Replication Server stable device.

  2. If there is not enough space in the stable device to increase the size of the log, add space to the stable device.

  3. Make sure the DSI thread to the data server and the RSI thread to the Replication Server are up and running.