Invalid RSI locater

An RSI locater points to the last message that the replicate Replication Server stable queue received from the primary Replication Server. The RSI uses the RSI locater in the rs_locater system table to delete messages in the stable queues. The replicate Replication Server updates the RSI locater in the rs_locater system table with the last messages that the replicate Replication Server added to its stable queues. Periodically, the primary Replication Server requests the RSI locater from rs_locater at the replicate Replication Server. The primary Replication Server deletes its stable queue messages up to and including the message identified by the RSI locater—these are the messages that the replicate Replication Server has already received.

NoteThe RSI locater is different from the locater that is used with database log truncation. See “Resetting the locater” for more information about the database log truncation locater.

If the RSI locaters at the primary and replicate Replication Servers are not identical, then the primary Replication Server might delete messages from its stable queue at an incorrect location and invalidate the RSI locater at the replicate Replication Server.

RSI locaters must be identical. If they are not identical:

  1. Make sure that the replicate Replication Server is not running.

  2. Set the replicate Replication Server RSI locater to “0” by executing this command against the replicate Replication Server RSSD:

    update rs_locater set locater=0x0
     where sender = primary_replication_server