
Diagnostics: Cumulative SQL Trace (DB2 UDB for UNIX and Windows)
You can access trace information on SQL statements by calling transaction DB6COCKPIT and choosing Diagnostics ® Cumulative SQL Trace in the navigation frame of the DBA Cockpit. The Diagnostics: Cumulative SQL Trace screen appears.
If you want to retrieve new data, choose
Refresh.
The following information is displayed on the EXECUTE, PREPARE and FETCH times of SQL statements:
|
Column |
Description |
|
Total Time |
Cumulative execution time of a statement |
|
% |
Proportional execution time of one statement with regard to all executed statements |
|
Count |
Number of executions |
|
Time/Stmt |
Average execution time of one statement |
|
Table |
Name of table the SQL statements reads from. If the statement reads from more than one table, only the name of the first table will be displayed on this screen. The other names are displayed under Statement Infos on the detail screen. |
|
SQL Statement |
Complete SQL statement |
If you want to display more detailed information, double click a line or select a line and choose
Details. The Cumulative SQL Trace - Details screen appears providing information on:
Displays the complete SQL statement, the application server where the statement was executed and the name of the ABAP Report in which the statement can be found
Displays the distribution times of the selected SQL statement
If you want to display the access plan for the execution of a single statement, select a line and choose
Explain. This function provides a detailed analysis of expensive SQL statements. For more information, see
To display the ABAP source program where the statement was defined, choose Source. An editor screen appears, which contains the related source.

Since all trace data remains permanently in the database, you should delete obsolete data before starting a new trace. To do this, choose
Delete on the Diagnostics: Cumulative SQL Trace screen.
For information on how to activate the cumulative SQL trace function, see SAP Note 139286.