Download as pdf or txt
Download as pdf or txt
You are on page 1of 16

HADR Monitoring

Wajeehuddin Samdani, SAP


Apr 10, 2019

CUSTOMER
System Status

Replication Path Status - checks the health and latency status of the replication paths.

sap_status path

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 2


System Status

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 3


States

▪ Defined – The state expected after setup and before materialization.

▪ Suspended – The state expected during materialization, when data flow is suspended while
waiting for load activities to complete.

▪ Down – The path is unavailable and replication is not occurring due to an error.

▪ Active – The replication path is supporting replication.

▪ Unknown – Path state cannot be determined.

▪ Incomplete – Failover is incomplete.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 4


Other information

▪ Last Commit Time – The local timestamp of a command applied to the target database.

▪ Latency – The approximate length of time it takes for an update on the source system to reach
the target, based on the last trace command sent.

▪ Latency Time – The timestamp of the most recent trace command that was applied to the target
database and used for the latency calculation

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 5


System Status

Replication Path Status - checks the health and latency status of the replication paths.

sap_status path

Replication Sub Components Status - monitors the status of the servers, threads and queues of the
replication path.

sap_status route

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 6


System Status

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 7


Name - Sequence description

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 8


System Status

Replication Path Status - checks the health and latency status of the replication paths.

sap_status path

Replication Sub Components Status - monitors the status of the servers, threads and queues of the
replication path.

sap_status route

Replication Queues Information - monitors the Replication Server device usage and queue backlog
and SAP ASE transaction log size and backlog.

sap_status resource

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 9


System Status

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 10


Tracing Latency

Send a trace to initiate latency monitoring.

sap_send_trace <primary_logical_host_name> [,<database_name>]

sap_status path

If there is a backlog of data, the trace element reflected by sap_status path results may not be the
most recent trace element requested. Verify that Time latency last calculated is the current time,
and not reflective of the trace element that was executed earlier.

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 11


Tracing Latency

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 12


Checking latency with rs_ticket

▪ Log into the primary SAP ASE server with isql as the DR_admin login.

▪ Switch to the database for which you need to investigate the replication latency.

▪ exec rs_ticket 'my_ticket'

▪ Log into the standby SAP ASE server with isql as the DR_admin login.

▪ Switch to the database for which you are investigating the replication latency.

▪ select pdb_t, exec_t, dist_t, dsi_t, rdb_t from rs_ticket_history where


h1='my_ticket'

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 13


Checking latency with rs_ticket

▪ Latency from the primary ASE server to the standby ASE server:
Calculate by rdb_t – pdb_t
▪ Latency from the primary ASE server to Replication Server internal threads:
Latency to EXEC thread: exec_t – pdb_t
Latency to DIST thread: dist_t – pdb_t
Latency to DSI thread: dsi_t – pdb_t

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 14


Checking latency DBA Cockpit

© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ CUSTOMER 15


Thank you.

Contact information:
Wajeeh Samdani
Senor Software Engineer
High Availability, DB/OS Porting Team

SAP SE
Dietmar-Hopp-Allee 16
69190 Walldorf, Germany

You might also like