last updated: 2026-01-02

Why was this blog post created?

There is a lot of confusion about the different types of trace files. When troubleshooting a problem, in many case the wrong trace file is collected.

It is important to be aware and understand that different trace types can be collected from the SAP HANA database and that they are suitable for identifying different problems. In some cases only Full System Info Dump (FSID) is needed, while in other cases Runtime Dump (RTE) is needed. In special cases, both may be needed.

Where can I find the most important information about the FSID and RTE?

SAP Community Article: Where can I find knowledge and information belongs to SAP HANA?

section Full System Info Dump (FSID)section Runtime Dump (RTE) Full System Info Dump (FSID)Runtime Dump (RTE)Issue timeHappened in the past.Happens in real time.When to use?Root Cause Analysis (RCA)Real-Time Analysis (RTA)When to collect?Anytime (but must include the time when the problem occurred, e.g. collected last 7 days of trace while issue occurred 3 days ago).Real time, when the issue occurs actually.ExamplesSystem crash, oom – out of memory issue, etc.High CPU, slow system, slow execution, unresponsive or hung system, blocked transaction, general performance issue, etc.How to analyze?Mainly manual trace checking/reviewing but there are tools also.

2498739 – How-To: Analyzing Runtime Dumps with SAP HANA Dump Analyzer

How to collect both FSID and RTE together to get the most detailed trace for complete investigation?

The following scenario explains the proper order of the trace collection activity.

Collecting RTE files (during the issue exists, while the system slow, unresponsive, hung or high CPU utilization , etc. observed).Restart the system manually (to bring the system back to normal/stable/working state) or wait until it performs well again (issue solved on its own, e.g. cause of the performance issue solved, long running execution finally finished, CPU usage dropped).Collecting FSID files (after the system restarted successfully or performance issue solved on its own and the system is up and running normally again).

What is the conclusion?

While issue reported to SAP it is a good practice to upload the relevant traces right away. This will speed up the case handling process.

Do you have further questions?

Please do not hesitate to contact me if you have question or observation regarding the article.
Q&A link for SAP HANA: https://answers.sap.com/tags/73554900100700000996

Contribution

If you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.

Release Information

Release DateDescription2026.01.02First/initial Release of the SAP Blog Post documentation (Technical Article).

last updated: 2026-01-02Why was this blog post created?There is a lot of confusion about the different types of trace files. When troubleshooting a problem, in many case the wrong trace file is collected.It is important to be aware and understand that different trace types can be collected from the SAP HANA database and that they are suitable for identifying different problems. In some cases only Full System Info Dump (FSID) is needed, while in other cases Runtime Dump (RTE) is needed. In special cases, both may be needed.Where can I find the most important information about the FSID and RTE?SAP Community Article: Where can I find knowledge and information belongs to SAP HANA?section Full System Info Dump (FSID)section Runtime Dump (RTE) Full System Info Dump (FSID)Runtime Dump (RTE)Issue timeHappened in the past.Happens in real time.When to use?Root Cause Analysis (RCA)Real-Time Analysis (RTA)When to collect?Anytime (but must include the time when the problem occurred, e.g. collected last 7 days of trace while issue occurred 3 days ago).Real time, when the issue occurs actually.ExamplesSystem crash, oom – out of memory issue, etc.High CPU, slow system, slow execution, unresponsive or hung system, blocked transaction, general performance issue, etc.How to analyze?Mainly manual trace checking/reviewing but there are tools also.2498739 – How-To: Analyzing Runtime Dumps with SAP HANA Dump AnalyzerHow to collect both FSID and RTE together to get the most detailed trace for complete investigation?The following scenario explains the proper order of the trace collection activity.Collecting RTE files (during the issue exists, while the system slow, unresponsive, hung or high CPU utilization , etc. observed).Restart the system manually (to bring the system back to normal/stable/working state) or wait until it performs well again (issue solved on its own, e.g. cause of the performance issue solved, long running execution finally finished, CPU usage dropped).Collecting FSID files (after the system restarted successfully or performance issue solved on its own and the system is up and running normally again).What is the conclusion?While issue reported to SAP it is a good practice to upload the relevant traces right away. This will speed up the case handling process.Other article✍️ Where can I find knowledge and information belongs to SAP HANA?✍️ Where can I find information about the available tools for SAP HANA (all types of use)?Do you have further questions?Please do not hesitate to contact me if you have question or observation regarding the article.Q&A link for SAP HANA: https://answers.sap.com/tags/73554900100700000996 ContributionIf you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.Release InformationRelease DateDescription2026.01.02First/initial Release of the SAP Blog Post documentation (Technical Article). Read More Technology Blog Posts by SAP articles

#SAP

#SAPTechnologyblog