When you start replication in the Replication Agent:
The Replication Agent instance opens network connections to the primary database and primary 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 Replication Agent instance goes from Admin state to Replicating state.
When the 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 Replication Agent instance must be running before you can start replication. See “Starting the Sybase Replication Agent” for more information.
To start replication in the Replication Agent
Log in to the Replication Agent instance with the administrator login.
Use the following command to start replication:
resume
After you invoke the resume command, the Replication Agent instance should go from Admin state to Replicating state.
Use the following command to verify that the Replication Agent instance is in Replicating state:
ra_status
If the Replication Agent instance does not go to Replicating state after you invoke the resume command, see Chapter 4, “Troubleshooting Sybase Replication Agent,” for more information.
See the Sybase Replication Agent Reference Manual for more detailed information about the resume command and how Sybase Replication Agent starts replication processing.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
