Symptom
In a system replication setup, on the secondary site there are many dumps of log shipping timeouts are generated/occurred.
In the secondary indexserver log, the following entries can be seen:
e sr_dataaccess DisasterRecoverySecondaryImpl.cpp(01121) : Trying to reconnect data handler to primary (1)
w PersistenceManag DisasterRecoveryProtocol.cpp(04578) : log buffer takes more than 30000000 us to process and write, this could be caused by write-IO peak.
w PersistenceManag DisasterRecoveryProtocol.cpp(04579) : This trace is intended to clarify frequent "logshipping timeout" situation. If this is the case, then it's probably by write-IO, not by network.
Read more...
Environment
SAP HANA, platform edition
Keywords
logshipping timeout, write-IO, network, replication, secondary, IO values, hardware , 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.