Stops all Sybase Replication Agent processing in Replicating state, and puts the Sybase Replication Agent instance in Admin state.
quiesce
When the quiesce command is invoked, it stops all current replication processing in the Sybase Replication Agent instance:
The Log Reader component stops reading operations from the transaction log as soon as the current scan is complete. It continues to send change-set data to the Log Transfer Interface component until it finishes processing the last operation scanned from the log.
The Log Transfer Interface component stops sending LTL commands to the Replication Server as soon as it finishes processing the last change set it receives from the Log Reader.
When the Log Transfer Interface component is finished processing its input queue and sending the resulting LTL, the Sybase Replication Agent instance releases all of its connections to the primary database, and drops its connection to the primary Replication Server (and RSSD, if connected).
The Sybase Replication Agent instance goes from Replicating state to Admin state.
If the Sybase Replication Agent internal queues are full when the quiesce command is invoked, the quiesce processing may take a while to complete, and there may be a delay before the Sybase Replication Agent instance completes its transition to Admin state.
Before moving the Sybase Replication Agent to the Admin state, the quiesce command waits until all data in the primary log has been read and sent to the Replication server.
If the Sybase Replication Agent instance is in Admin state, the quiesce command returns an error.
The quiesce command is valid only when the Sybase Replication Agent instance is in Replicating state.
The action of the suspend command
is similar to that of the quiesce command, except
that the suspend command stops Sybase Replication Agent processing
immediately and flushes all data in the internal queues.
