Stops all Mirror Replication Agent processing in Replicating state, and puts the Mirror Replication Agent instance in Admin state.
quiesce
When the quiesce command is invoked, it stops all current replication processing:
The Log Reader component stops reading operations from the mirror log devices 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 Mirror Replication Agent instance releases all of its connections to the primary database (if any are open), and drops its connection to the Replication Server (and RSSD, if connected).
The Mirror Replication Agent instance goes from Replicating state to Admin state.
If the Mirror 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 Mirror Replication Agent instance completes its transition to Admin state.
If the Mirror Replication Agent instance is in Admin state, the quiesce command returns an error.
The quiesce command is valid only when the Mirror 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 Mirror Replication Agent processing
immediately and flushes all data in the internal queues.
