Before you attempt to replicate transactions from the primary database, you must complete all of the procedures in “Setting up Mirror Replication Agent connectivity”.
Starting replication in the Mirror Replication
Agent instance
Log in to the Mirror Replication Agent administration port, and use the following command to verify that the Mirror Replication Agent instance is in Admin state:
ra_status
Start replication by invoking the following command:
resume
Use the ra_status command to verify that the Mirror Replication Agent instance is in Replicating state.
The Mirror Replication Agent instance goes to the Replicating
state only if a connection for the primary database has been created
in the primary Replication Server. For more information on creating
the primary database connection in Replication Server, see the Mirror
Replication Agent Primary Database Guide.
When the Mirror Replication Agent instance is in Replicating state, it is scanning the transaction log for transactions to be replicated and sending LTL to the primary Replication Server.
If the Mirror Replication Agent instance is not in Replicating state after you invoke the resume command, see Chapter 4, “Troubleshooting Mirror Replication Agent” for more information.
