Quiescing the Replication Agent instance stops its replication processing gracefully, ensuring that all transactions from the log have been read and sent to the Replication Server:
The Log Reader component stops reading operations from the transaction log when 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 it 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 received from the Log Reader.
When the Log Transfer Interface component is finished processing its input queue and sending the resulting LTL, the 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 Replication Agent instance goes from Replicating state to Admin state.
To quiesce a Replication Agent instance
Log in to the Replication Agent instance with the administrator login.
Use the following command to quiesce the Replication Agent:
quiesce
After you invoke the quiesce command, the Replication Agent instance should go from Replicating state to Admin state.
Use the following command to verify that the Replication Agent instance is in Admin state:
ra_status
If the internal queues are full and the primary database
is still recording new activity to the log files when you invoke
the quiesce command, the quiesce processing may
take a while to complete, and there may be a delay before the Sybase Replication Agent instance
completes the transition to admin state.
For more detailed information about the quiesce command and its processing, see the Sybase Replication Agent Reference Manual.
