Replication Server Interface Problems

Replication Server Interface (RSI) allows two Replication Servers to exchange transactions across a route. Usually, RSI problems occur when Replication Server attempts to connect to another Replication Server or when the locater is invalid.

Although many errors may occur when a primary Replication Server loses its connection to the replicate Replication Server, none of these errors should cause a loss of data or cause the RSI to be suspended. The primary thread continuously attempts to connect to the replicate Replication Server until the connection is reestablished.

Losing the connection terminates the RSI thread at the replicate Replication Server. The thread at a replicate Replication Server exists only while a connection exists. Executing admin who in the replicate Replication Server shows that the primary Replication Server is no longer logged in as an RSI source. When the primary Replication Server reestablishes the connection to the replicate Replication Server, data is replicated across the route to the replicate Replication Server.

• Incorrect RSI User Login Name or Password
  The primary Replication Server logs in to the replicate Replication Server using the Replication Server Interface (RSI) login name and password. The RSI user login name and password are created by rs_init and are also required when you create a route to the replicate Replication Server.
• Incorrect User Permissions at Replicate Replication Server
  The Replication Server Interface (RSI) login must have connect source or sa permission on the replicate Replication Server. If the login lacks the appropriate permission, an error message is sent to the primary Replication Server error log.
• Invalid RSI Locater
  An invalid Replication Server Interface (RSI) locater indicates that the RSI locaters at the primary and replicate Replication Servers are not identical, and that the primary Replication Server deleted messages from its stable queue at an incorrect location.