SAP HANA Studio Trace Configuration
This page introduces the various system traces available with SAP HANA which can be used to collect diagnostic information.
SAP HANA Studio Trace Configuration
SAP HANA Studio provides a graphical user interface for enabling and configuring a number of the most common and important traces.
To access the trace configuration in SAP HANA Studio, open the HANA System in the SAP HANA Administration Console Perspective and click onto the Trace Configuration tab.
Prerequisites
To configure traces, you must have the system privilege TRACE ADMIN. To configure the kernel profiler, you must have the SAP_INTERNAL_HANA_SUPPORT standard role.
The table below shows the list of traces which can be configured from within SAP HANA Studio, their default status and the primary distinguishing purpose of that trace.
Available Traces
Trace
|
Default Status
|
Purpose
|
Related Content
|
|---|---|---|---|
| Database Trace | Active |
The database trace records information about activity in the components
of the SAP HANA database. You can use this information to analyze performance and to diagnose and debug errors. <more> | |
| SQL Trace | Inactive | The SQL trace collects information about all executed SQL statements and saves it in a trace file for further analysis. It is inactive by default.
Information collected includes overall execution time of each statement, the number
of records affected, potential errors (for example, unique constraint violations) that were reported, the database connection being used, and so on. <more> | |
| User-Specific Trace | Inactive |
The user specific trace is used to trace activity through the available components
(i.e. IndexServer, NameServer) for a specific application or database user. | |
| Performance Trace | Inactive | The performance trace is a performance tracing tool built into the SAP HANA database. It records performance indicators for individual query processing steps in the database kernel. It is inactive by default.
Information collected includes the processing time required in a particular step, the data
size read and written, network communication, and information specific to the operator or processing-step-specific (for example, number of records used as input and output). <more> | How to use HDBAdmin to analyze performance traces in SAP HANA |
| End-To-End Traces | Inactive | The predefined end-to-end traces are used by applications to trace activity through all the available trace components. i.e. IndexServer, NameServer | |
| Expensive Statements Trace | Inactive | Expensive statements are individual SQL statements whose execution time exceeded a configured threshold. <more> | SAP HANA Academy - Using the Expensive Statements Trace |
| Kernel Profiler | Inactive |
The kernel profiler is a sampling profiler built into the SAP HANA database. It can be used
to analyze performance issues with systems on which third-party software cannot be installed, or parts of the database that are not accessible by the performance trace. <more>
Caution To be able to use the kernel profile, you must have the
SAP_INTERNAL_HANA_SUPPORT role. This role is intended only for SAP HANA development support. |
Locating the Trace/Diagnostic Files
Diagnosis files include log and trace files, as well as a mixture of other diagnosis, error, and information files. In the event of problems with the SAP HANA database, you can check these diagnosis files for errors.
You can access diagnosis files on the Diagnosis Files tab of the Administration editor.
To access the files from the operating system level, they are stored at the following default location: /usr/sap/<SID>/HDB<instance>/<host>/trace.