Use the procedures in this chapter to successfully solve problems that occur after executing a create route, alter route, or drop route command. Each procedure requires you to obtain and analyze information from the Replication Server error logs, execute the rs_helproute stored procedure, or both.
To learn how to use the rs_helproute stored procedure and interpret its results, see “Using the rs_helproute stored procedure” and the Replication Server Reference Manual.
A route is one-way message stream from a source Replication Server to a destination Replication Server. Routes carry data modification commands (including those for RSSDs) and replicated functions or stored procedures between Replication Servers.
There are two types of routes—direct and indirect. A direct route sends messages directly from source to destination Replication Servers, with no intermediate Replication Servers. An indirect route sends messages through one or more intermediate Replication Servers.
Routes are created, altered, and dropped according to the following general procedure. The rs_marker stored procedure contains the full create route, alter route, or drop route command.
The source Replication Server executes the rs_marker stored procedure against its RSSD.
The RSSD’s RepAgent picks up the stored procedure execution and forwards it to the source Replication Server.
The source Replication Server appends the stored procedure execution to its inbound queue and forwards it to the destination Replication Server. The identity of the destination Replication Server is obtained from parameters in the stored procedure.
The destination Replication Server processes the stored procedure execution, which materializes subscriptions to the primary Replication Server RSSD rs_routes, rs_subscriptions, rs_rules, and rs_locater system tables.
