Starts replication processing in the Replication Agent instance.
Replication Agent attempts to open network connections to the primary database, primary Replication Server, and RSSD.
If it fails to establish a connection, Replication Agent logs a warning message in its system log, and it attempts to retry the connection, based on its configuration parameters for the connection.
If Replication Agent cannot establish a connection to the primary database after exhausting its configured retry attempts, it aborts all subsequent resume processing, returns to Replication Down state, and logs the error.
Replication Agent requests the current LTM Locator value from the primary Replication Server, and it stores the value in the Replication Agent transaction log.
The Log Reader component begins scanning the transaction log, looking for operations to be replicated. Log Reader begins scanning the log at the point identified by the LTM Locator value.
When it finds transactions to replicate, Log Reader passes them (as change-set data) to the input queue of the Log Transfer Interface component.
The Log Transfer Interface component reads the change-set data from its input queue, generates LTL commands, and places the LTL commands in its output queue for transmission to Replication Server.
When resume resync is invoked, the Replication Agent instance attempts to start in the Replicating (Resynchronization) state.
Replication Agent sends a resync database marker to Replication Server, which processes this resync database marker and awaits a dump database marker from Replication Agent.
When pdb_xlog init, force is invoked before resume resync, Replication Agent sends instructions for Replication Server to purge all open transactions from the inbound queue and reset duplicate detection before receiving any new inbound transactions. Replication Server then awaits a dump database marker from Replication Agent.
When resume resync, init is invoked, Replication Agent sends a resync database marker and an initialization command instructing Replication Server to purge all open transactions from the inbound queue, reset duplicate detection, and suspend the outbound DSI. Use this option when you want to reload the primary database from the same dump as the replicate database.
For more information about configuring database resynchronization, see the Replication Server Administration Guide.
When resume purge is invoked, the Replication Agent instance sends a purge command to Replication Server when replication resumes. Replication Server will then purge data from the inbound queue for the connection to which this Replication Agent instance is connected. The purge keyword should be used only after downgrading to an earlier version of Replication Agent or when otherwise recommended by Sybase Technical Support.
If any start-up operation fails, the Replication Agent instance returns to Replication Down state, and it logs the error.
If the resume command is successful, the Replication Agent instance goes to Replicating state. To determine the current state of Replication Agent, use the ra_status command.
The Replication Agent instance is already in Replicating state.
The system data repository in the RASD does not exist or is not initialized (Oracle and Microsoft SQL Server).
The Replication Agent connection configuration parameters are not set correctly, or it fails otherwise to connect with the primary database or the primary Replication Server.
The database connection for the primary database is not defined correctly in the primary Replication Server.
If the resume command is successful, the Replication Agent instance goes into Replicating state.
The resume command is valid only when the Replication Agent instance is in the Admin or Replication Down state.