Table of Contents
Understanding SAP HANA Full System Info Dump (FSID) vs Runtime Dump (RTE)
When diagnosing complex SAP HANA issues, it is critical to use the correct type of diagnostic dump. SAP provides two primary dump types that serve different troubleshooting needs:
- Full System Info Dump (FSID)
- Runtime Dump (RTE)
This post explains the differences, ideal use cases, and how and when to generate each type of dump.
📌 What Is a Full System Info Dump (FSID)?
A FSID (Full System Information Dump) collects extensive diagnostic data from an SAP HANA system. It includes trace files, configuration information, system properties, history, and runtime dumps — all organized in a ZIP file that can be analyzed later. FSIDs are especially useful when comprehensive system context is required.
The FSID can be imported into supportability tools such as SAP HANA Supportability Tools in Visual Studio Code for offline analysis. This allows performance experts to review traces, topology, and dump details in a structured interface.
👉 For more details on how to collect this comprehensive dump, check the official SAP guide on Collect and Download Diagnosis Information.
📌 What Is a Runtime Dump (RTE)?
A Runtime Dump (RTE) is generated manually or via commands to capture the active environment at a specific point in time. This includes thread stacks, memory state, SQL execution context, and system statistics related to processes that are running.
In contrast to a full system dump, RTE dumps are useful for isolating a current fault or unusual behavior within the SAP HANA runtime environment. RTE dumps do not include all the configuration and trace info that an FSID comprises.
👉 You can also create RTE dumps via SQL commands such as ALTER SYSTEM CREATE RUNTIMEDUMP as documented in SAP Help Portal.
🆚 FSID vs RTE – When to Use Which?
| Feature | Full System Info Dump (FSID) | Runtime Dump (RTE) |
|---|---|---|
| Scope | Comprehensive system data | Snapshot of live runtime state |
| Best For | Deep investigation, support upload, full context | Fault isolation, thread/process issues |
| Includes | Traces, configs, topology, explanations | Thread stacks, statistics, call stacks |
In some cases, support may ask for both FSID and RTE dumps to correlate issues efficiently. Understanding when each is needed helps you collect the right files with minimal system impact.
📌 Common Use Cases
- When SAP Support requests detailed diagnostics, use FSID.
- If a specific process or thread appears to behave unexpectedly, capture an RTE dump.
- For performance issue analysis, combining RTE and FSID provides deeper insights.
🔧 How to Analyze Dumps
SAP HANA provides supportability and dump analysis tools that allow offline and online analysis of FSID and RTE dumps:
- Run the Analysis – SAP Help Portal (shows analysis UI and dump support).
- Recommendations for Trace and Dump Files (official guide on dump collection).
🔗 Related Internal Resources
For detailed SAP troubleshooting guidance, check these related posts on my blog:
📣 Final Thoughts
Understanding the difference between Full System Info Dump (FSID) and Runtime Dump (RTE) allows you to collect the right diagnostics when troubleshooting SAP HANA systems. Using the correct dump type helps reduce time spent in analysis and ensures support teams have the information they need to resolve issues efficiently.
If you found this article useful, consider sharing it with #SAPBasis professionals and administrators!
#SAP #SAPHANA #FSID #RTE #SAPTroubleshooting #SAPSupport #SAPBasis #DumpAnalysis
“`