Show TOC

Tracing in the SAP HANA DatabaseLocate this document in the navigation structure

Use

If errors occur in queries, or performance problems arise with the SAP HANA database, it can help to record system responses as traces. SAP support has tools to evaluate these traces. To record traces for query execution, use the Query Monitor (see Query Monitor). If you are using the SAP HANA database, the same parameters are relevant as when using any other database with a SAP NetWeaver Business Warehouse Accelerator. Therefore, you can use the same standard traces (for the SAP HANA database) as you use for a BWA. There are two other standard traces for BWA. If using the SAP HANA database, these traces can be created with the DBA Cockpit (see DBA Cockpit for SAP HANA).

Procedure

Tracing Queries in the Query Monitor (RSRT)

In the Query Monitor, you can execute and debug queries.

  1. Select the query that you want to record a standard trace for.

  2. Choose Execute + Debug. The Debug Options dialog box appears. The options are ordered in a hierarchy.

  3. Choose Start of the navigation path SAP HANA/BWA Next navigation step SAP HANA/BWA Default Trace End of the navigation path.

    If you set the flag for SAP HANA/BWA Default Trace, the system automatically activates all traces listed under this option. These record information about the query currently being executed.

    You also have the option of selecting just one trace type.

Trace Type

Description

Python Trace

The index server is traced. The system generates an executable Python program.

To find out the selections for a query for example, SAP support can reproduce a query (without recording the ABAP read interface).

Plan/Performance Trace

A trace is recorded for the executing SAP HANA database component. The system generates an executable program.

To analyze the steps that the SAP HANA database performs, SAP support can reproduce a query (without recording the ABAP read interface).

Display

Once you have activated a trace type, the system displays the trace that the query was executed by. You can make changes to the trace file and save it locally.

Large trace files can cause runtime problems. You can therefore also save a trace file without displaying or changing it.

More Information