2222249 - How-To: Resolving SAP HANA Service Inconsistencies between Daemon and Topology

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

One of the following symptoms indicates that a SAP HANA service isn't properly started:

Tool	Symptom
SAP HANA Studio -> Administration -> Landscape -> Services	A red traffic light is displayed for one or several services:
SAP HANA Studio -> Configuration -> Alerts SAP Note 1969700 -> SQL: "HANA_StatisticsServer_Alerts_Current" -> SQL: "HANA_StatisticsServer_Alerts_History"	Alert 3 is permanently triggered with a rising number of <seconds>: The active status of <service> on host <host_name>, port <port> has been NO for <seconds> seconds.
SAP Note 1969700 -> SQL: "HANA_Services_Overview" (EXCLUDE_STARTED_SERVICES = 'X')	Services are returned with STARTED = 'NO': ---------------------------------------------------------------------- \|HOST \|PORT \|SERVICE_NAME \|TYPE \|STARTED\|SQL_PORT\|PROCESS_ID\| ---------------------------------------------------------------------- \|saphana001\|30200\|webdispatcher \|NONE \|NO \| 0\| 0\| ----------------------------------------------------------------------
M_SERVICES	A SELECT from M_SERVICES returns a service with ACTIVE_STATUS = 'NO'.
SQL: "HANA_Configuration_MiniChecks" (SAP Note 1999993)	Check ID M2130 is flagged as potentially critical (C = 'X').

SAP HANA

SAP HANA, platform edition all versions

compileserver; indexserver; nameserver; preprocessor; sapwebdisp; xsengine; daemon; M_TOPOLOGY_TREE; , KBA , HAN-DB , SAP HANA Database , How To

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Visit SAP Support Portal's SAP Notes and KBA Search.