2022-03-07 2783547

2783547 - Troubleshooting HADR issues in SAP ASE

16.0 environment - SRS
SAP Knowledge Base
Version 13 Type
Article
Master
Language English English
Language
Release
Released to Customer Category How To
Status
BC-SYB-REP-SAP (Replication with SAP Suite /
Component Released On 29.09.2021
SAP BW)

Please find the original document at https://launchpad.support.sap.com/#/notes/2783547

Symptom

How to troubleshoot HADR issues in SAP ASE 16.0 environment

Environment

• SAP Replication Server (SRS) 16.0

• SAP Adaptive Server Enterprise (ASE) 16.0 with Always-on Option (HADR)
• SAP Adaptive Server Enterprise (ASE) 16.0 for Business Suite with High Availability and Disaster
Recovery (HADR)

Resolution

• Information about the HADR environment

• From an isql session, log to RMA agent as DR_admin user:

isql -UDR_admin -P<password> -S<hostname>:<RMA port>

• There are several RMA Agent commands you can execute to get more information about HADR
environment:

1. sap_version all /* Displays versions of ASE/RS/RMA Agent in both, Primary & Standby,
sites */
2. sap_set /* Displays all the settings in the environment, including ports, host names, and
user names */
3. sap_status path /* Displays status of replication */
4. sap_status task /* Displays the asynchronous task status */
5. sap_status resource /* Monitors the Replication Server device usage and queue backlog
and SAP ASE transaction log size and backlog */
6. sap_status route /* Displays the sequence of queues, servers and threads in the
replication path */
7. sap_status synchronization /* Displays synchronization status */

• The best way to provide this information is to collect them into a text file.
• Use the following process to capture them:
1. Create file HADR_CMD.sql which contains the following command

© 2022 SAP SE or an SAP affiliate company. All rights reserved 1 of 5

2022-03-07 2783547

sap_version all
go
sap_set
go
sap_status
go
sap_status resource
go
sap_status task
go
sap_status path
go
sap_status route
go
sap_status synchronization
go

Note: Sometimes, information between the primary node and secondary node are out
of sync so it is necessary to check both nodes.

2. Execute file HADR_CMD.sql with program isql on primary node, and capture result in a
text file HADR_CMD_PRIM_RESULT.txt

isql -UDR_admin -Pxxxxxx -S<PRIMARY_RMA_NAME> -e -w400 -iHADR_CMD.sql -

oHADR_CMD_PRIM_RESULT.txt

3. Execute file HADR_CMD.sql with program isql on secondary node, and capture result in a
text file HADR_CMD_SEC_RESULT.txt

isql -UDR_admin -Pxxxxxx -S<SECONDARY_RMA_NAME> -e -w400 -

iHADR_CMD.sql -oHADR_CMD_SEC_RESULT.txt

4. Review the files HADR_CMD_PRIM_RESULT.txt and HADR_CMD_SEC_RESULT.txt,

and verify there are no errors reported.

In case of errors, review the commands in HADR_CMD.sql and ensure they are
correctly copied without any typo.
If the cause of the error is not identified, then report it to SAP Support.

5. Provide result files into the incident.

• Review logs

• In ASE 16.0 SP03 and higher, use RMA command, sap_collect_log to collect ASE/RS/RMA logs
of different hosts to one local directory $SYBASE/DM/collected_logs:

sap_collect_log [, <logical_host_name>] [, <number_of_days>]

• If RMA command, sap_collect_log is not available, the log files location for version ASE 16.0 are:
• Replication Server log files

$SYBASE/DM/<CID>_REP_<logical_site>/<CID>_REP_<logical_site>.log

• DR (RMA) Agent log file

© 2022 SAP SE or an SAP affiliate company. All rights reserved 2 of 5

2022-03-07 2783547

$SYBASE/DM/RMA-16_0/instances/AgentContainer/logs/RMA_*.log

• Data Server ASE logs

$SYBASE/ASE-16_0/install/*.log

• SAP installer logs (Installer issues)

$SYBASE/ASE-16_0/init/logs

• Setup HADR logs (setuphadr issues)

$SYBASE/ASE-16_0/init/logs
Note: To collect logs for an incident, use RMA command, sap_collect_log (in SP03 or
higher) to collect ASE/RS/RMA logs of different hosts to one local directory
$SYBASE/DM/collected_logs.

• Check replication in active SRS (companion usually):

admin who
go
admin who_is_down
go
admin who, sqm
go
admin who, sqt
go
admin disk_space, mb
go
admin stats, mem_detail_stats
go

• In primary ASE, check RepAgent:

sp_configure 'replication agent memory'

go

sp_who
go

use <database>
go

sp_config_rep_agent <database>
go

sp_helpdb <database>
go

• For Fault Manager or failover issues:

• Fault Manager error log

$SYBASE/<SIDFM>/log/dev_sybdbfm

© 2022 SAP SE or an SAP affiliate company. All rights reserved 3 of 5

2022-03-07 2783547

• SYBHA.PFL

Documentation/Known issues

• Installing HADR with an Existing System

• HADR Users Guide
• Command sap_status
• Recovering from a Failed Setup
• Performing a Teardown

See Also

• KBA 2305518 - Troubleshooting HADR issues in ASE 15.7 Business Suite environment
• KBA 2175528 - FAQ HADR with SAP Replication Server certified for Business Suite
• KBA 2616427 - How to gather all log files in HADR ASE 16.0 SP03 and higher

Keywords

Sybase, HADR, troubleshooting, DR Agent, RMA, setuphadr, active, standby, sap_status, materialize

Products

SAP Adaptive Server Enterprise 16.0

SAP Replication Server 16.0

Other Components

Component Description

BC-DB-SYB Business Suite on Adaptive Server Enterprise

BC-SYB-REP Sybase Replication Server (standalone)

This document refers to

SAP Note/KBA Title

2616427 How to gather all log files of a HADR system - SRS

2379871 How to refresh the latency calculation time in a HADR environment - SRS

2305518 Troubleshooting HADR issues in a ASE 15.7 Business Suite environment

2175528 FAQ HADR with SRS certified for Business Suite

© 2022 SAP SE or an SAP affiliate company. All rights reserved 4 of 5

2022-03-07 2783547
2165143 How to perform a planned or unplanned failover - SAP ASE and SRS

2089569 How to re-materialize master or SID databases - SAP ASE and SRS

Recovering from a Failed Setup

HADR Users Guide

Installing HADR with an Existing System

Performing a Teardown

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2022 SAP SE or an SAP affiliate company. All rights reserved 5 of 5