Before you attempt to replicate transactions from the
primary database, you must complete all of the procedures in “Setting up Replication Agent connectivity”.
To start replication in the Replication Agent
instance
Log in to the Replication Agent administration port, and use the following command to verify that the 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 Replication Agent instance is in Replicating state.
The 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 Replication
Agent Primary Database Guide.
When the 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 Replication Agent instance is not in Replicating state after you invoke the resume command, see Chapter 4, “Troubleshooting Replication Agent” for more information.