Symptom
1. From primary RMA log, there is following error
xxxx-01-28 00:00:00 [WARN ] [pool-2-thread-2:73][RMA] - [ConnectionManager ] - getConnection: JZ00L: Login failed. Examine the SQLWarnings chained to this exception for the reason(s).
xxxx-01-28 00:00:00 [ERROR] [Thread-100859:116146][RMA] - [RepServerModel ] - Unable to connect to a 'Replication Server' at '<hostname>:<SRS port>' with credential ('sapsa'). However the server appears to be running.
2. When log in primary ASE using 'sapsa', and query RMA proxy table (see sample below), it will report error
1> select * from master..hadrStatusSynchronization
2> go
LogicalHost Hostname hadrMode hadrState SynchronizationMode DBName SynchronizationState
---------------------------------------------------------------- -------------------------------------------------------------------------------------------------------------------------------- -------------------------------- -------------------------------- -------------------------------- -------------------------------- --------------------------------
site1 <hostname> Primary Active Synchronous NULL Error
site1 <hostname> Primary Active Synchronous master Error
site1 <hostname> Primary Active Synchronous <SID> Error
(3 rows affected)
3. When log in primary ASE using DR_admin and query the table above, the output shows correct SynchronizationState
4. Check external login using sapsa to log in primary ASE, it shows there is defined role mapping which means any login that has replication_role will be mapped to DR_admin when logging in primary RMA server - ABC_site1_DRA
1> sp_helpexternlogin
2> go
Server Login Externlogin
---------- -------- -----------
ABC_SECDR DR_admin DR_admin
SYB_JSTASK sapsa sapsa
loopback sa sa
(3 rows affected)
Server Roles Externlogin
----------- ---------------- -----------
ABC_site1_DRA replication_role DR_admin
(1 row affected)
5. Check sapsa roles by logging in primary ASE and run following, it indeed has active replication_role
1> sp_activeroles expand_down
2> go
Role Name Parent Role Name Level
------------------------------ ------------------------------ ------
sap_adm NULL 1
sybase_ts_role NULL 1
js_admin_role sap_adm 2
replication_role sap_adm 2
sa_role sap_adm 2
sap_mon sap_adm 2
mon_role sap_mon 3
(7 rows affected)
(return status = 0)
Read more...
Environment
SAP Adaptive Server Enterprise Always-on (HADR) with SAP Business Suite
Product
Keywords
KBA , BC-SYB-REP-SAP , Replication with SAP Suite / SAP BW , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview