Resume the Mirror Replication Agent instance

This section describes the commands you must issue to resume a Mirror Replication Agent instance.

To resume the Mirror Replication Agent instance

The resume command puts the Mirror Replication Agent in a REPLICATING state, reading the ASE active log and sending commands to Replication Server.

To place the Mirror Replication Agent in a REPLICATING state, enter the resume command:
```
resumego
```
If the Mirror Replication Agent successfully transfers to a REPLICATING state, this result is returned:
```
State                                    Action
```
```
-----------------------------------  -------------------------
```
```
REPLICATING (WAITING AT END OF LOG)  Ready to replicate data.
```
If the state returned is ADMIN, an error prevented the REPLICATING state from being achieved. To determine the error, review the contents of the Mirror Replication Agent instance log. Also, see the Mirror Replication Agent Administration Guide, Chapter 2, “Troubleshooting Mirror Replication Agent,” and the section titled, “Examining the Mirror Replication Agent when replication failure occurs.”
The ra_status command returns the state of the Mirror Replication Agent. It is good practice to verify that the Mirror Replication Agent remains in REPLICATING state, even after the resume command executes successfully.

To detect an error that occurred after replication start-up, execute the ra_status command:
```
ra_statusgo
```
If the Mirror Replication Agent is in REPLICATING state, this result is returned:
```
State                                      Action
```
```
-----------------------------------   -------------------------
```
```
REPLICATING  (WAITING AT END OF LOG)  Ready to replicate data.
```
If the state returned is ADMIN, an error prevented the REPLICATING state from being achieved. To determine the error, review the contents of the Mirror Replication Agent instance log.

Also, see the Mirror Replication Agent Administration Guide, Chapter 2, “Troubleshooting Mirror Replication Agent,” and the section titled, “Examining the Mirror Replication Agent when replication failure occurs.”

To validate that both primary and standby connections are active, issue the admin who command:

isql -Usa -P -SSAMPLE_RS 
admin who 
go

You should not proceed until admin who has a status for threads similar to this:

Spid Name      State            Info

---- --------- ---------------- --------------------------------------

30   DSI EXEC  Awaiting Command 101(1) SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD

22   DSI       Awaiting Message 101 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD

18   SQM       Awaiting Message 101:0 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD

47   DSI EXEC  Awaiting Command 102(1) repit151i2.foo2

23   DSI       Awaiting Message 102 repit151i2.foo2

19   SQM       Awaiting Message 102:0 repit151i2.foo2

46   DSI EXEC  Awaiting Command 103(1) repit151i.foo

24   DSI       Awaiting Message 103 repit151i.foo

26   DIST      Awaiting Wakeup  103 repit151i.foo

29   SQT       Awaiting Wakeup  103:1 DIST repit151i.foo

21   SQM       Awaiting Message 103:1 repit151i.foo

20   SQM       Awaiting Message 103:0 repit151i.foo

53   REP AGENT Awaiting Command repit151i.f00

25   dSUB      Sleeping

15   dCM       Awaiting Message

17   dAIO      Awaiting Message

27   dREC      Sleeping         dREC

54   USER      Active           sa

14   dALARM    Awaiting Wakeup

28   dSYSAM    Sleeping