Troubleshooting guide

Command <resume> failed - Desired state <REPLICATE>
could not be achieved. Current state: <REPLICATION DOWN>
3.
The ra_status command returns the state of the Replication Agent. It is a good practice to
verify that the Replication Agent remains in replication state, even after the resume
command executes successfully.
To detect an error that occurred after replication start-up, execute:
ra_status
go
If the Replication Agent is in replicating state, ra_status returns:
State Action
----------------- -------------------------
REPLICATING Ready to replicate data.
The Replication Agent goes to the REPLICATION DOWN state if an error occurs:
1> ra_status
2> go
State Action
----------------- -----------------------
REPLICATION DOWN Waiting for operator command.
4.
Validate that both primary and replicate connections are active:
isql -Usa -Psa_pass -SSAMPLE_RS
admin who
go
Note: Be aware that:
• The DSI connection for the primary database connection is usually suspended 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) rds.rdb
53 DSI Awaiting Message 102 rds.rdb
17 SQM Awaiting Message 102:0 rds.rdb
20 DSI EXEC Suspended 103(1) pds.pdb
21 DSI Suspended 103 pds.pdb
24 DIST Awaiting Wakeup 103 pds.pdb
25 SQT Awaiting Wakeup 103:1 DIST pds.pdb
23 SQM Awaiting Message 103:1 pds.pdb
CHAPTER 4: Oracle-to-SAP HANA Database Replication Setup
46 Replication Server