Initialize the Replication Agent instance.
ra_admin init go
You see a message indicating that the procedure was successful.
resume go
State Action ----------------- -------------------------- REPLICATING Ready to replicate data.
1> resume 2> go Msg 32000, Level 20, State 0: Server 'rao', Procedure 'resume', Line 1: Command <resume> failed - Desired state <REPLICATE> could not be achieved. Current state: <REPLICATION DOWN>
ra_status go
State Action ----------------- ------------------------- REPLICATING Ready to replicate data.
1> ra_status 2> go State Action ----------------- ----------------------- REPLICATION DOWN Waiting for operator command.
isql -Uusername -Ppassword -SSAMPLE_RS admin who go
The DSI connection for the primary database connection is usually down because you are not replicating data back to the primary database.
The Replication Agent connection, if established for the replicate database connection, is usually down, because you are not replicating data from the replicate database.
Do not proceed until admin who returns status for threads similar to this:
Spid Name State Info ---- --------- --------- -------------------------------------- 13 DSI EXEC Awaiting Command 101(1) SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD 9 DSI Awaiting Message 101 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD 8 SQM Awaiting Message 101:0 SAMPLE_RS_ERSSD.SAMPLE_RS_ERSSD 54 DSI EXEC Awaiting Command 102(1) orcl1.oratest2 53 DSI Awaiting Message 102 orcl1.oratest2 17 SQM Awaiting Message 102:0 orcl1.oratest2DSI 20 DSI EXEC Suspended 103(1) NY.NYora92 21 DSI Suspended 103 NY.NYora92 24 DIST Awaiting Wakeup 103 NY.NYora92 25 SQT Awaiting Wakeup 103:1 DIST NY.NYora92 23 SQM Awaiting Message 103:1 NY.NYora92 22 SQM Awaiting Message 103:0 NY.NYora92 62 REP AGENT Awaiting Command NY.NYora92