The "Troubleshoot Unresponsive System" application within the SAP HANA cockpit is the designated tool for investigating a system that is offline, hung, or otherwise unresponsive to normal SQL connections. This application provides functionality to connect to the sapstartsrv service on the host, even when the database itself is not responding. It allows an administrator to trigger the creation of critical diagnostic files, such as runtime dumps (RTE dumps), which are essential for performing a root cause analysis of the unresponsive state. This makes it the primary tool for this specific emergency scenario.

A. Alert Monitor: This application requires an active connection to a running database to retrieve and display alerts, making it unsuitable for an offline system.

B. Full System Information Dumps: While this collects comprehensive diagnostic data, the "Troubleshoot Unresponsive System" app is the specific tool designed to initiate diagnostics when the system is inaccessible.

D. Performance Monitor: This tool is used to analyze performance metrics (CPU, memory, etc.) of an online and operational system and cannot function if the system is offline.

1. SAP HANA Cockpit Administration Guide

section "Troubleshooting an Unresponsive System". The documentation states

"If an SAP HANA system is unresponsive

you can use the Troubleshoot Unresponsive System app in the SAP HANA cockpit to investigate the situation. For example

you can create runtime dumps to analyze the current state of all server processes." (SAP Help Portal

SAP HANA Platform 2.0 SPS 07).

2. SAP HANA Administration Guide for SAP HANA Platform

section "Troubleshooting Unresponsive Systems". This guide details the process

noting that tools like the hdbcons command line or the SAP HANA cockpit's "Troubleshoot Unresponsive System" app are used to trigger runtime dumps when a system is hung. (SAP Help Portal

SAP HANA Platform 2.0 SPS 07).