Symptom
You notice long takeover time in HANA system replication environment.
The following traces are noticed:
<timestamp> i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01322) : Prepare takeover started (operationMode=logreplay; replicationStatus=ReplicationStatus_Active) ..
<timestamp> i PersistenceManag DisasterRecoverySecondaryImpl.cpp(01344) : Takeover: invalidating connections
<timestamp> i sr_dataaccess DisasterRecoverySecondaryImpl.cpp(01545) : Takeover: primary (2.00.0XX.00.XXXXXX) and secondary version are different (2.00.0YY.00.YYYYYYY), this can result in increased takeover time!
Read more...
Product
Keywords
takeover, secondary version are different, increased, system replication , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , 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.