Evaluating SQL Traces

Prerequisites

You are in the Troubleshooting Database Open SQL Monitors SQL Trace Evaluation function of SAP NetWeaver Administrator.
You have activated the SQL trace for the selected cluster node.

More information: Managing the SQL Trace

Context

You use this procedure to evaluate finished and currently running SQL traces. Traces in the Available SQL Traces for Evaluation area are initially sorted in the order they are written in.

Procedure

To sort the list by one of the columns, click the column header.

To enable or disable the column filter, choose the pushbutton. To filter the table, enter a filter string in the appropriate column header.
To view a particular trace, select the trace and choose Display Selected Trace .

Records are initially sorted in the order they are written in. Trace records are displayed according to the returned native JDBC method.

Note

You can filter trace records by date and time, or by advanced selection criteria. To filter trace records by one or more of the advanced selection criteria, choose the Advanced Filter button.

Note

By default, the number of trace records in the list is limited to 10,000 records. To change the limit, choose the Advanced Filter button and enter the appropriate number in the Max. Number of Records field. If there are trace records that are not displayed due to this limit, the SQL Trace List function shows a Trace contains more data than currently displayed warning.

To view details for a particular record, select a record from the SQL Trace List . The Record Details screen area opens.

Attribute	Meaning
Time	The exact start time of the JDBC method call in millisecond precision
Duration in Microseconds	The duration of the method call in microseconds (10-6s)
Method Name	The name of the JDBC method call that was traced.
JDBC Method Input Parameters	JDBC call input parameters
DB Error Code	The error code in case an error occurs
DB Error SQL State	The database SQL state in case an error occurs
Statement	The SQL statement (or JDBC method call) that is executed
SQL Statement Bind Parameters	All bind parameters.
Result	The result of a JDBC method call
Database Id	A string identifying the database connection used. Currently a combination of data source name (as defined in JDBC Connector Service) and database user, delimited by an ampersand ("&").
Number of Calls	Number of subsequent calls with the same result (compound record)
Minimum Duration of a Single Call in Microseconds	Minimum duration of a single JDBC method call (compound record)
Maximum Duration of a Single Call in Micro Seconds	Maximum duration of a single JDBC method call (compound record)
Average Duration of a Single Call in Micro Seconds	Average duration of a single JDBC method call (compound record)
J2EE Application	Name of the current Java EE application
J2EE User	The user name of the current Java EE user
J2EE Transaction	Identifier of the current Java EE transaction
J2EE Sessio	Identifier of the current Java EE session
ResultSet Id	An identifier for the ResultSet object. It is needed to relate ResultSets to the statements they originate from.
Table names	All involved tables (available only in case OpenSQL was used).
Thread	The thread executing the JDBC method
DB Session Id	The ID of the database session as reported by the RDBMS.
Vendor SQL Connection Id	Identifier for the Vendor SQL connection
Vendor SQL statement Id	Identifier for the Vendor SQL statement
Stack Trace	The stack trace (in case it was enabled)
DSR Transaction Id	The distributed statistical records identifier.
Unique log record number	SQL Trace uses the general SAP Logging and Tracing mechanism. The SAP Logging API trace record number thus appears in the trace.

Next Steps

SQL Trace Analysis Example