SAP Knowledge Base Article - Preview

2534122 - System Replication takeover takes longer than expected SAP HANA

Symptom

In your Disaster Recovery setup you have found the time to complete a takeover takes much longer than expected.

The System Replication Status was 'Active' and in Sync before the primary was disabled and takeover initiated.

Replication from Primary site to Secondary site is with Operation Mode 'logreplay'.

From the service traces on secondary site (those with persistence) the last redo log position before the takeover execution has a timestamp from a long time ago.

For Example:

indexserver_<host>.#####.###.trc
...
[11355]{-1}[-1/-1] < Todays Date and time>i Logger           RecoveryHandlerImpl.cpp(00679) : Redo done up to position: <#######> and time: < (Today date  & time) - n>
...

Read more...

Environment

SAP HANA 1.0 Revision 122.06 or earlier

Product

SAP HANA 1.0, platform edition

Keywords

Logreplay, hang, sr_takeover, stuck , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, etc.) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.