To check the status of SAP HANA Database Replication, you can use any of the following methods,
Method 1
Navigate to this path
/usr/sap/[SID]/HDB[xx]/exe/python_support
Execute the command python systemReplicationStatus.py
python systemReplicationStatus.py
|Database |Host |Port |Service Name |Volume ID |Site ID |Site Name |Secondary |Secondary |Secondary |Secondary |Secondary |Replication |Replication |Replication |Secondary |
| | | | | | | |Host |Port |Site ID |Site Name |Active Status |Mode |Status |Status Details |Fully Synced |
|-------- |------------- |----- |------------ |--------- |------- |--------- |------------- |--------- |--------- |--------- |------------- |----------- |----------- |-------------- |------------ |
|SYSTEMDB |HANA1 |30201 |nameserver | 1 | 1 |DC1 |HANA2 | 30201 | 2 |DC2 |YES |ASYNC |ACTIVE | | True |
|SID |HANA1 |30203 |indexserver | 2 | 1 |DC1 |HANA2 | 30203 | 2 |DC2 |YES |ASYNC |ACTIVE | | True |
status system replication site "2": ACTIVE
overall system replication status: ACTIVE
Local System Replication State
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mode: HANA1
site id: 1
site name: DC1
Alternatively, you can use the below command to check the status of the primary system.
python landscapeHostConfiguration.py
Method 2
Use command below,
hdbcons -e hdbindexserver "replication info"
SAP HANA DB Management Client Console (type '\?' to get help for client commands)
Try to open connection to server process 'hdbindexserver' on system 'SID', instance 'XX' and tenant 'SID'
SAP HANA DB Management Server Console (type 'help' to get help for server commands)
Executable: hdbindexserver (PID: 5015)
Service: indexserver@HANA1:3XX03 (DB#3: SID)
[OK]
--
## Start command at: 2026-04-23 09:58:21.169
listing default statistics for volume 2
System Replication Primary Information
======================================
System Replication Primary Configuration
[ system_replication] logshipping_timeout = 30
[ system_replication] enable_full_sync = false
[ system_replication] preload_column_tables = true
[ system_replication] ensure_backup_history = true
[ system_replication_communication] enable_ssl = on
[ system_replication] keep_old_style_alert = false
[ system_replication] enable_log_retention = auto
[ system_replication] logshipping_max_retention_size = 1048576
- lastLogPos : 0x3157593c40
- lastLogPosTimestamp : 23.04.2026-01.58.21 (1776909501112897)
- lastConfirmedLogPos : 0x3157593c40
- lastConfirmedLogPosTimestamp: 23.04.2026-01.58.21 (1776909501112897)
- lastSavepointVersion : 384823
- lastSavepointLogPos : 0x3157565843
- lastSavepointTimestamp : 23.04.2026-01.56.51 (1776909411388153)
1 session registered.
Session index 0
- SiteID : 2
- RemoteHost : 192.169.1.10
Log Connection
- ptr : 0x00007f3c524bd000
- channel : {<NetworkChannelSSLFilter>={<NetworkChannelBase>={this=139897071299608, fd=185, refCnt=2, idx=1, local=192.169.1.11/4XX03_tcp, remote=192.169.1.10/21710_tcp, state=Connected, pending=[r---]}}}
- SSLActive : true
- mode : async
Data Connection
- ptr : 0x00007ecba7366000
- channel : {<NetworkChannelSSLFilter>={<NetworkChannelBase>={this=139479616975896, fd=339, refCnt=2, idx=3, local=192.169.1.11/4XX03_tcp, remote=192.169.1.10/21946_tcp, state=Connected, pending=[r---]}}}
- SSLActive : true
Primary Statistics
- Creation Timestamp : 18.04.2026-00.53.01 (1776473581725479)
- Last Reset Timestamp : 18.04.2026-00.53.01 (1776473581725479)
- Statistic Reset Count : 0
- ReplicationMode : async
- OperationMode : logreplay
- ReplicationStatus : ReplicationStatus_Active
- ReplicationStatusDetails :
- ReplicationFullSync : DISABLED
- shippedLogPos : 0x3157593c40
- shippedLogPosTimestamp : 23.04.2026-01.58.21 (1776909501112897)
- sentLogPos : 0x3157593c40
- sentLogPosTimestamp : 23.04.2026-01.58.21 (1776909501112897)
- sentMaxLogWriteEndPosition : 0x3157593c40
- sentMaxLogWriteEndPositionReqCnt: 0x20e833
- shippedLogBuffersCount : 4717710
- shippedLogBuffersSize : 35568861184 bytes
- shippedLogBuffersSizeUsed : 28785016576 bytes (80.93%)
- shippedLogBuffersSizeNet : 28785016576 bytes (80.93%)
- shippedLogBufferDuration : 10421063811 microseconds
- shippedLogBufferDurationMin : 2 microseconds
- shippedLogBufferDurationMax : 37240922 microseconds
- shippedLogBufferDurationSend : 10421063811 microseconds
- shippedLogBufferDurationComp : 0 microseconds
- shippedLogBufferThroughput : 3413190.79 bytes/s
- shippedLogBufferPendingDuration : 17451291932 microseconds
- shippedLogBufferRealThrougput : 2038213.35 bytes/s
.......
.........
............
----------------------------------------------------------------
[OK]
## Finish command at: 2026-04-23 09:58:21.173 command took: 89.000 usec
--
[EXIT]
--
[BYE]
Method 3
Open SAP HANA Studio and log in to the SYSTEMDB. From the Overview page, you can then check the System Replication Status.
You can click on System Replication Status to view the detailed information.
Method 4
You can achieve the same result directly in SAP using transaction code DB02 or DBACOCKPIT. Under Current Status, double-click Overview. On the right-hand panel, you will see the System Replication Status.
Click it to view the detailed information.
