SAP Knowledge Base Article - Preview

2188812 - Indexserver not starting on secondary node after takeover

Symptom

After successful failover from primary to secondary node, the indexserver does not start on the secondary.

This can occur in rare circumstances.

The indexserver trace file contains the following as its latest entry

PersistenceManag PersistenceManagerImpl.cpp(02359) : Activating periodic savepoint, frequency 300

 

 


Read more...

Environment

HANA 1.0

Product

SAP HANA 1.0, platform edition

Keywords

KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , HAN-DB-ENG , SAP HANA DB Engines , Bug Filed

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.