Troubleshooting guide

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.
Replication Agent goes to the REPLICATION DOWN state if an error occurs.
isql –Usa –Psa_pass –SSAMPLE_RS
1> resume
2> go
Msg 32000, Level 20, State 0:
Server 'myra', Procedure 'resume', Line 1:
Command <resume> failed - Desired state <REPLICATE>
could not be achieved. Current state: <REPLICATION
DOWN>
3.
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:
admin who
go
You see:
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
8 SQM Awaiting Message 101:0 SAMPLE_RS_ERSSD.
SAMPLE_RS_ERSSD
54 DSI EXEC Awaiting Command 102(1)
my_mssql_access_service.rdb
53 DSI Awaiting Message 102
my_mssql_access_service.rdb
17 SQM Awaiting Message 102:0
my_mssql_access_service.rdb DSI
CHAPTER 5: Microsoft SQL Server-to-SAP HANA Database Replication Setup
74 Replication Server