3797621 - SAP HANA System Replication — HA Hook Kills Secondary Node During Initial Full Data Transfer

Symptom

During SAP HANA System Replication initial full data transfer, the secondary node is unexpectedly shut down mid-sync. After the shutdown, all replication channels from the primary lose connectivity with errors such as:

```

CONNECTION TIMEOUT / Communication channel closed

```

The secondary indexserver trace shows the replication was in progress (e.g., ~81% of total data transferred) immediately before shutdown:

```

setStatusDetails(): Secondary: Full Replica: 81 % (XXXX/XXXX GB), isCloseMessage=0, isCloseMessageSet=0

```

Followed by a shutdown sequence:

```

Shutdown requested while service startup still running - will wait 1 minute for the startup to finish

process is terminating -> aborting nameserver retries

Preparing for shutting service down

Preparing to shutdown

```

The nameserver trace shows the HA/DR provider hook (`susChkSrv`) declared the indexserver as lost and issued a stop action:

```

srv:indexserver-<port>-no-yes db:<SID>-<instance>-yes daem:yes

LOST: indexserver event looks like a lost indexserver (status=no)

LOST: stop instance. action_on_lost=stop

Environment

SAP HANA PLATFORM EDITION 2.0

Keywords

indexserver startup failure, persistence startup error, could not read anchorpage, exception 3000284, anchorpage invalid savepoint version, suschksrv, action_on_lost, system replication, full replica, connection timeout, nameserver watchdog, savepoint, hana scale-out, re-register secondary, force full replica , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , BC-OP-LNX , Linux , HAN-DB , SAP HANA Database , 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.