When you start replication in the Mirror Replication Agent:
Mirror Replication Agent opens network connections to the primary database, Replication Server, and RSSD.
The internal Log Reader and Log Transfer Interface components begin their 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.
See the description of the resume command in Chapter 4, “Mirror Replication Agent Command Reference,” for more detailed information about how Mirror Replication Agent starts its normal replication processing.
Before you attempt to replicate transactions from a
mirror log device, use the checklist in “Setting up the Mirror Activator system” to verify that your Mirror Activator system
is set up properly.
The Mirror Replication Agent instance must be running before you can start replication. See “Starting the Mirror Replication Agent” for more information.
To start 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.
Use the following command to verify that the Mirror Replication Agent instance is in Replicating state:
ra_status
If the Mirror Replication Agent instance does not go to Replicating state after you invoke the resume command, see Chapter 6, “Troubleshooting Mirror Replication Agent,” for more information.
