Suspend and Resume Routes

When you alter a direct route, change its topology, or perform some other maintenance to a remote site, you must suspend the route so that messages are no longer sent to the destination Replication Server. After maintenance is completed for the route, you can then reactivate the route to resume activity.

You can suspend and resume routes in Sybase Central or with the suspend route and resume route RCL commands.

You can suspend and resume dedicated routes with suspend route and resume route. See Replication Server Administration Guide Volume 2 > Performanc Tuning > Multi-Path Replication > Dedicated Routes.

suspend route

suspend route suspends a route to another Replication Server.

While a route is suspended, no messages are sent to the destination Replication Server, and the messages for the Replication Server are held in a stable queue. The syntax for the suspend route command is:

suspend route to dest_replication_server
[with primary at dataserver.database]

Include the with primary at dataserver.database clause in the command to specify a dedicated route, where dataserver.database is the primary connection name.

For example, to suspend the route to the CHI_RS Replication Server, enter:

suspend route to CHI_RS

resume route

resume route resumes a suspended route.

Resuming a route allows the source Replication Server to begin sending queued messages to the destination Replication Server. You can also use this command to resume a route that was suspended automatically as the result of an error. The syntax for the resume route command is:

resume route to dest_replication_server
[with primary at dataserver.database | 
skip transaction with large message]

Include the with primary at dataserver.database clause in the command to specify a dedicated route, where dataserver.database is the primary connection name.

For example, to resume the route to the CHI_RS Replication Server, enter:

resume route to CHI_RS