Suspend Log Transfer

Execute suspend log transfer to disconnect one or all RepAgents and prevent RepAgents from connecting to Replication Server.

Log transfer to Replication Server remains suspended until you resume it using the resume log transfer command.

suspend log transfer command records information in the RSSD, so if you shut down Replication Server and restart it, log transfer to that Replication Server remains suspended.

Note: Suspending log transfer is the first step in quiescing the replication system.

To suspend log transfer, log in to Replication Server and execute suspend log transfer at the isql prompt by entering:

suspend log transfer from {data_server.database | all}

where:

data_server – the data server with the database for which log transfer is to be suspended.
database – the database for which log transfer is to be suspended.
all – instructs Replication Server to suspend log transfer from all RepAgent and disallow future connections for all RepAgent.

These examples demonstrate the use of suspend log transfer .

Suspend log transfer for the database named pubs2, managed by the TOKYO_DS data server:
```
suspend log transfer from TOKYO_DS.pubs2
```
Suspend log transfer to the current Replication Server from all RepAgents:
```
suspend log transfer from all
```

In both examples, after the command is executed, affected RepAgent are not shut down and may continue to send some messages to Replication Server. To shut down a RepAgent immediately, log in to Adaptive Server and enter sp_stop_rep_agent, with the name of the database for which RepAgent is enabled, and the nowait option.