Starts replication processing in the Mirror Replication Agent instance.
resume
When resume is invoked, the Mirror Replication Agent instance attempts to start replication and go to Replicating state, as follows:
Mirror Replication Agent attempts to open network connections to the primary database, Replication Server, and RSSD.
If it fails to establish a connection to the primary
database, the Mirror Replication Agent logs a warning message in its system log and
attempts to retry the connection, based on its configuration parameters
for the connection.
Mirror Replication Agent checks the RASD to make sure it contains a valid system data repository, and validates its read access to the mirror log devices.
Mirror Replication Agent requests the current LTM Locator value from the Replication Server, and it stores the LTM Locator value in the RASD.
The Log Reader component begins scanning the primary database transaction log on the mirror log devices, looking for operations to be replicated. Log Reader begins scanning the transaction 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 to send to the Replication Server, and passes the LTL commands to its output queue for transmission to the Replication Server.
If any startup operation fails, except establishing a connection to the primary database, the Mirror Replication Agent instance returns to Admin state, and it logs the error.
If the resume command is successful, the Mirror Replication Agent instance goes to Replicating state. To determine the current state of the Mirror Replication Agent, use the ra_status command.
The resume command returns an error under any of the following conditions:
The Mirror Replication Agent instance is already in Replicating state.
The system data repository in the RASD does not exist.
The Mirror Replication Agent connection configuration parameters are not set correctly, or it fails otherwise to connect with the Replication Server.
The database connection for the primary database is not defined correctly in the Replication Server.
The Mirror Replication Agent connection configuration parameters are not set correctly.
The resume command is valid only when the Mirror Replication Agent instance is in Admin state.
