When you stop replication in the Mirror Replication Agent:
The internal Log Reader and Log Transfer Interface components stop their normal replication processing.
Any open connections to the primary database are released, and the connection to the Replication Server is dropped.
The Mirror Replication Agent instance goes from Replicating state to Admin state.
When the Mirror Replication Agent instance is in Admin state, it is running and available to execute administrative commands, but it does not maintain connections to the primary database and Replication Server (and RSSD, if so configured), and it does not process replicated transactions.
Some administrative tasks require the Mirror Replication Agent instance to be in Admin state. In a normal operating Mirror Activator system, you must stop replication in the Mirror Replication Agent to perform those tasks.
There are two ways to stop replication in the Mirror Replication Agent:
Quiesce the Mirror Replication Agent instance to stop replication gracefully. For more information, see “Quiescing the Mirror Replication Agent”.
Suspend the Mirror Replication Agent instance to stop replication immediately. For more information, see “Suspending the Mirror Replication Agent instance”.
