The message below is displayed in the Replication Server error log after you executed a rebuild queues command (which is typically issued after a stable device failed).
You should check for data loss detection messages in the Replication Server error log only after you have issued the rebuild queues command and the data loss detection process has completed. Data loss detection should only be performed when there are primary transactions to be replicated. The RSM heartbeats feature replicates a primary transaction to the destination data server. You can activate the heartbeats feature for the connection to force data loss detection to be performed.
Sometimes these messages are not displayed at the end
of the error log file, so you must search back through the log for
them. If you restart the Replication Server, these messages will
be displayed again.
I. 96/10/02 13:31:19. DSI: detecting loss for database 'westss.eastlp' from origin 'westss.norttp' date = 'Oct 2 1996 12:01:35:313PM', qid=00000001004fc7ac0000fb0e0016ffffffff000000008a0a00c630b20001000000000003. I. 96/10/02 13:31:19. DSI: no transactions for database 'westss.norttp' from origin 'westss.eastlp' will be applied or deleted from the queue, because loss was detected. I. 96/10/02 13:33:08. LTM for westss.eastlp connected in passthru mode. I. 96/10/02 14:31:28. Disconnecting LTM for westss.eastlp. LTM will shut down I. 96/10/02 14:31:32. Resetting LTM Starting Log Position for westss.eastlp I. 96/10/02 14:31:34. Shutting down distributor for 106 I. 96/10/02 14:31:34. The distributor for 'westss.eastlp' is Shutting Down I. 96/10/02 14:31:36. Disconnecting LTM for westss.eastlp to Rebuild I. 96/10/02 14:31:36. Shutting down the DSI thread for 'westss.eastlp'. I. 96/10/02 14:31:36. The DSI thread for database 'westss.eastlp' is shutdown. I. 96/10/02 14:31:36. DSI: enabled loss detection for 'westss.eastlp'. I. 96/10/02 14:31:40. Rebuild Queues: Deleting Queue 106:1 I. 96/10/02 14:31:40. SQM Stopping: 106:1 westss.eastlp I. 96/10/02 14:31:40. Rebuild Queues: Done Rebuilding Queue 106:1. Restarting I. 96/10/02 14:31:40. SQM starting: 106:1 westss.eastlp I. 96/10/02 14:31:40. Rebuild Queues: Deleting Queue 106:0 I. 96/10/02 14:31:41. SQM Stopping: 106:0 westss.eastlp I. 96/10/02 14:31:41. Rebuild Queues: Done Rebuilding Queue 106:0. Restarting I. 96/10/02 14:31:41. SQM starting: 106:0 westss.eastlp I. 96/10/02 14:31:47. Starting the distributor for 'westss.eastlp'. I. 96/10/02 14:31:49. Starting the DSI thread for 'westss.eastlp'. I. 96/10/02 14:31:50. The DSI thread for database 'westss.eastlp' is started. I. 96/10/02 14:31:51. DSI: detecting loss for database 'westss.eastlp' from origin 'westss.norttp' date = 'Oct 2 1996 12:01:35:313PM', qid=00000001004fc7ac0000fb0e0016ffffffff000000008a0a00c630b20001000000000003. I. 96/10/02 14:36:22. LTM for westss.eastlp connected in passthru mode. I. 96/10/02 14:36:22. Restarting LTM for westss.eastlp at the beginning of the log I. 96/10/02 14:36:33. LTM for westss.eastlp connected in passthru mode. I. 96/10/02 14:53:32. DSI: no transactions for database 'westss.norttp' from origin 'westss.eastlp' will be applied or deleted from the queue, because loss was detected. I. 96/10/02 14:53:32. DSI: detecting loss for database 'westss.norttp' from origin 'westss.eastlp' date = 'Oct 2 1996 12:01:28:313PM', qid=0000000100764b0e0000fb0c000affffffff000000008a0a00c6287e0001000000000001. I. 96/10/02 14:53:35. DSI: loss detected for database 'westss.norttp' from origin 'westss.eastlp'. I. 96/10/02 15:00:02. LTM for westss.eastlp connected in passthru mode. I. 96/10/02 15:00:17. DSI: loss detected for database 'westss.eastlp' from origin 'westss.norttp'.
Replication Server detected loss for a primary Replication Server or database. User transactions from the primary Replication Server or database are no longer accepted. If the replication system has more than one Replication Server, then the detected data loss could be either a DSI loss or an RSI loss. If the replication system has only one Replication Server, the detected data loss is a DSI loss. A DSI loss means that data was not replicated from the Replication Server to the replicate database. An RSI loss means that data was not replicated from one Replication Server to another Replication Server.
For information on correcting data losses, see Chapter 19, “Replication System Recovery,” of the Replication Server Administration Guide.
To prevent data loss, use DSI or RSI save intervals to create a backup strategy with backlogs large enough to keep all messages.