SAP Knowledge Base Article - Preview

1905462 - Topology mismatch leads to recovery failure on multi-host system

Symptom

On a distributed SAP HANA System, running on Single Database Container, database recover fails with the following error in backup.log:

RECOVERY RECOVER DATA finished with error: [110092] Recovery failed in 
nameserver startup: convert topology failed, mismatch: 1
statisticsservers configured in source topology, 0 standby in source
topology, 2 in destination system, mismatch: 1 xsengines configured in
source topology, 0 standby in source topology, 2 in destination system

Meanwhile, if you check the daemon.ini file for different nodes on SAP HANA server, you'll see there're 2 nodes having the same content in their daemon.ini, for example:

cat hananode01/daemon.ini
[sapwebdisp]
instances = 1
[statisticsserver]
instances = 1
[xsengine]
instances = 1
cat hananode02/daemon.ini
[sapwebdisp]
instances = 1
[statisticsserver]
instances = 1
[xsengine]
instances = 1


Read more...

Environment

SAP HANA, platform edition

Product

SAP HANA, platform edition all versions

Keywords

convert topology failed, mismatch, daemon.ini, sapwebdisp, scale out, scale-out, failover, worker, worker, multi-host , KBA , HAN-DB-BAC , SAP HANA Backup & Recovery , HAN-DB , SAP HANA Database , How To

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.