DSI detected rs_update_lastcommit not marked as replicated

Symptom

A warm standby database disconnects and these error messages are displayed in the Replication Server error log:

I. 2006/06/13 15:39:53. DSI for %RS_SITEID detected that
stored procedure rs_update_lastcommit is not marked as
replicated. Please execute sp_setreplicate and resume
connection
When active DSI comes up in presence of the Warm Standby
it checks whether rs_update_lastcommit stored procedure
is marked as  replicated. This DSI detected a problem
with replication status of  this stored procedure.
Please, correct the problem and resume connection

Explanation

This error occurs during a warm standby installation. You have used isql to execute the create connection command and did not mark rs_update_lastcommit as replicated.

Solution

  1. Set replication status on rs_update_lastcommit by marking it with the sp_setrepproc system procedure.

  2. Resume connection.

Instead of using the create connection command, you can use rs_init to create a connection to a warm standby database. This message does not occur when you use rs_init to set up the warm standby.

When you use rs_init to set up your active and standby database, the rs_update_lastcommit stored procedure is automatically marked for replication.