Hi Mohammed,
The same user and password that you use to connect to the DR Agent can be used to connect to the Replication Server.
The default port number assigned to your Replication is typically 4 less than the DR Agent port.
So - if I use isql to log into my DR Agent on port 4909:
isql -UDR_admin -Pmypass -Ssapdr2:4909
I can likely log into the Replication Server on the same host at port 4905
isql -UDR_admin -Pmypass -Ssapdr2:4905
Once logged on, command 'admin version' will return the version string of the Replication Server.
1> admin version
2> go
Version
-------------------------------------------------------------------------------------------------------------------------------
Replication Server/15.7.1/EBF ..../Linux 2.6.18-128.el5 x86_64/1/OPT64/Fri May 2 08:56:36 2014
Comamnd 'admin who' lists the main threads in the Replication Server
1> admin who
2> go
Spid Name State Info
---- --------------- -------------------- ------------------------------------------------------------
21 DSI EXEC Awaiting Command 101(1) RMA_REP_HANARep_RSSD.RMA_REP_HANARep_RSSD
15 DSI Awaiting Message 101 RMA_REP_HANARep_RSSD.RMA_REP_HANARep_RSSD
14 SQM Awaiting Message 101:0 RMA_REP_HANARep_RSSD.RMA_REP_HANARep_RSSD
DSI EXEC Suspended 102(1) UDBPrimary.SDM
DSI Suspended 102 UDBPrimary.SDM
192 DIST Awaiting Wakeup 102 UDBPrimary.SDM
193 SQT Awaiting Wakeup 102:1 DIST UDBPrimary.SDM
25 SQM Awaiting Message 102:1 UDBPrimary.SDM
24 SQM Awaiting Message 102:0 UDBPrimary.SDM
45 REP AGENT Awaiting Command UDBPrimary.SDM
In the example above, the "DSI" and "DSI EXEC" threads that are 'Awaiting...' are in a natural state.
The "DSI" and "DSI EXEC" threads that are 'Suspend' are not. In your env, I am expecting the DSI threads for 'TSD_sapdr2.TSD' may have a state of 'Down'.
If you issue command 'admin log_name', Replication Server will display the name of the log file for the Replication Server.
Regards,
Stephen