Understanding Replication Agent states

When a Replication Agent instance is running, it can be in one of two discrete states:

NoteWhen the state appears as Replicating (Waiting at end of log), the instance is ready to perform (or continue) its normal replication processing, but the Log Reader component is idle and waiting for additional transactions to be logged.

The default start-up state is Admin. The Replication Agent instance goes to Admin state automatically when no start-up state is specified.

The state of a Replication Agent instance can be changed by either:

From the moment a state-changing event occurs until the Replication Agent instance is actually in the new state, the instance is said to be “in transition.” During state transition, some administrative commands are ignored.

Admin state

A Replication Agent instance goes to Admin state when:

In Admin state, the Replication Agent instance is running, but it has no connection established to the primary Replication Server (or RSSD, if so configured) or the primary database.

You can perform most administrative tasks while the Replication Agent instance is in Admin state, including changing the value of any Replication Agent configuration parameter.

NoteIn Admin state, the instance can open a connection to the primary database, if necessary, to process a command that requests results from the primary database.

A Replication Agent instance may go to Admin state from Replicating state when a network failure or communication error causes its connection to the primary database or the primary Replication Server to be dropped.

When Replication Agent drops a connection, before it goes to Admin state, it first attempts to re-establish the connection using the values recorded in its configuration parameters for that connection. If it cannot reconnect, the Replication Agent instance goes to Admin state.

Replicating state

A Replication Agent instance goes to Replicating state when:

In Replicating state, the Replication Agent instance maintains a connection 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.

If the Replication Agent instance has finished processing all of the records in the transaction log, its state may appear as Replicating (Waiting at end of log). In that case: