Show TOC

resume route to a replication serverLocate this document in the navigation structure

Resumes a suspended route to another (destination) Replication Server.

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

The name of the destination Replication Server.

with primary

Specifies the connection from the primary database that you want to resume a dedicated route for.

skip transaction with large message

Ignore first transaction encountered with a message greater than 16,000 bytes.

Example 1

Resumes the route to the SYDNEY_RS Replication Server:

resume route to SYDNEY_RS
Example 2

To resume the dedicated route (between the RS_NY primary Replication Server and the RS_LON replicate Replication Server) for the NY_DS.pdb1 primary connection at RS_NY, enter:

resume route to RS_LON
 with primary at NY_DS.pdb1
  • Resuming a route allows Replication Server to begin sending queued messages to the remote Replication Server again.

  • resume route can also be used to resume a route suspended because of an error.

  • skip transaction with large message is applicable only to direct routes where the site version at the replicate site is 12.1 or earlier.


resume route requires “sa” permission.