Symptom
For MDC system, indexserver service fails to start.
You can see the following error messages in traces.
- Daemon trace:
i Daemon Program.cpp(00173) : line up of program group indexserver to instances <none>.
i Daemon Program.cpp(00173) : line up of program group indexserver.c to instances <none>.topology.txt
i Daemon Program.cpp(00173) : line up of program group indexserver.<SID> to instances 40.
- Nameserver trace:
e MultiDB TREXNameServer.cpp(05532) : Splitting DatabaseId and VolumeId from -1:2 failed. DatabaseId = VolumeId =
- Topology.txt
indexserver=
30003=
activated_at=<timestamp>
active=no
pid=00000
start_time=<timestamp>
index=
volumes=
-1:2=
active=no
catalog=yes
database=xxxxxxxxxx
initialization_in_progress=yes
location=<hostname>:<port>
path=mnt00001/hdb00002.xxxxx
servicetype=indexserver
-1:3=
active=no
database=xxxxxxxxxx
initialization_in_progress=yes
location=<hostname>:<port>
path=mnt00001/hdb00003.xxxxx
servicetype=indexserver
......
-1:n=
active=no
database=xxxxxxxxxx
initialization_in_progress=yes
location=<hostname>:<port>
path=mnt00001/hdb0000n.xxxxx
servicetype=indexserver
Read more...
Environment
- As of SAP HANA Database 1.0 SPS9
- SAP HANA Database 2.0
Product
SAP HANA, platform edition all versions
Keywords
topology, topology.ini, daemon.ini, Multi Database Container, SYSTEMDB, tenant , KBA , HAN-DB-ENG , SAP HANA DB Engines , 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.