When you start replication in the Mirror Replication Agent:
The Mirror Replication Agent instance opens network connections to the primary database and Replication Server (and the RSSD, if so configured).
The internal Log Reader and Log Transfer Interface components begin normal replication processing, scanning the transaction log for operations to replicate, and sending replicated transactions to the Replication Server.
The Mirror Replication Agent instance goes from Admin state to Replicating state.
When the Mirror Replication Agent instance is in Replicating state, it maintains connections to the primary database and the primary Replication Server (and RSSD, if so configured), and its Log Reader component scans the transaction log for transactions to replicate.
The Mirror Replication Agent instance must be running before you can start replication. See “Starting Mirror Replication Agent”.
Before you attempt to replicate transactions from a
log device, use the checklist in “Setting up the Mirror Activator system” to verify that your Mirror Activator system
is set up properly.
Starting replication in the Mirror Replication
Agent
Log in to the Mirror Replication Agent instance with the administrator login.
Use the following command to start replication:
resume
After you invoke the resume command, the Mirror Replication Agent instance should go from Admin state to Replicating state.
If the Mirror Replication Agent instance does not go to Replicating state after you invoke the resume command, see Chapter 4, “Troubleshooting Mirror Replication Agent,” for more information.
Use the following command to verify that the Mirror Replication Agent instance is in Replicating state:
ra_status
See the Mirror Replication Agent Reference Manual for more detailed information about the resume command and how Mirror Replication Agent starts replication processing.
