Invalid RSI Locater

Kevin Clymans

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 you need to reset the correct entry in the rs_locater system table in the Replication Server System Database (RSSD)

Stores the last locator field received by stable queues from each of their senders.

Column Datatype Description
sender int Sender site ID
type char(1) Who is using this row:

  • R – RSI (route)
  • D – distributor locater used for subscriptions
  • E – executor for Replication Agent
  • U – locator at last system upgrade
  • W – distributor locator used for a warm standby application
  • C – locater for the last successfully executed replication definition request sent by Replication Agent.
  • F – locater for failed command sent by Replication Agent.
  • S – locater for failed command that Replication Server skipped.
locater binary(36) Last queue ID received from this sender

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 Replication Server System Database (RSSD):

    update rs_locater set locater=0x0 where sender = primary_replication_server