SAP Knowledge Base Article - Preview

2927380 - After indexserver crash, Tenant database does not start due to network communication problems

Symptom

  • After a crash on indexserver, the database fails to start with the following errors:
    [00000]{-1}[-1/-1] 2020-04-13 00:45:47.778205 f indexserver TREXIndexServer.cpp(00945) : Nameserver setStarting call failed with errorcode=5500 msg=nameserver communication error;failed to send setStarting to master.
    [00000]{-1}[-1/-1] 2020-04-13 00:45:47.778492 e assign TREXIndexServer.cpp(01092) : Exception: exception 1: no.70005500 (TREXIndexServer2/TREXIndexServer.cpp:946)
    nameserver communication error;failed to send setStarting to master.
    exception throw location:
    1: 0x000055e16b4c5958 in nlsui_main+0xea4 at TrexService.cpp:601 (hdbindexserver)
    2: 0x00007fa649bc4554 in System::mainWrapper(int, char**, char**)+0x20 at IsInMain.cpp:327 (libhdbbasis.so)
    3: 0x00007fa647bc8545 in __libc_start_main+0xf1 (libc.so.6)
    [00000]{-1}[-1/-1] 2020-04-13 00:45:47.782247 f Service TrexService.cpp(00604) : FATAL: set service started failed
  • Your SAP HANA system has 2 or more nodes (distributed system);
  • SAP HANA runs on Multitenant Database Containers (MDC) mode;

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


Read more...

Environment

  • SAP HANA, platform edition 

Product

SAP HANA, platform edition all versions

Keywords

SAP HANA, sap_hana, database, db, platform edition, hana1, hana2, 1.0, 2.0, NetException, crash, crashed, database, restart, not starting, don't start, won't start , KBA , 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.