This page summarizes the contents of the trace file selected in the Trace Files Page.
To open the Summary page
Click SQL & Application Workload | Analyze Trace | Trace Files.
Data on the Summary page
| Data | Description |
|---|---|
|
Trace File Name |
The name of the Oracle trace file. |
|
Number of Statements |
The number of SQL statements in the trace file. |
|
Total CPU (s) |
The total CPU time for all parse, execute and fetch calls, and the retrieval of any underlying views for the specified SQL statement, measured in seconds. |
|
SQL Elapsed Time (s) |
The total server execution time of the parse, execute, fetch and wait operations for the execution of the specified SQL statement, measured in seconds. |
|
Total Disk |
The total number of disk reads for parses, executions and fetches. These are known as database block reads from disk. The disk read statistic is incremented once per block read regardless of whether the read data request was for a multi-block read or a single-block read. Most physical reads load data, index, and rollback blocks from the disk into the buffer cache. |
|
Total Logical Reads |
The total number of logical data block reads. These include data block reads from both memory and disk. Input/output is one of the most expensive operations in a database system. I/O-intensive statements can monopolize memory and disk usage, causing other database applications to compete for these resources. |
|
Start Time |
The time of the first entry in the trace file. |
|
End Time |
The time of the last entry in the trace file. |
Charts on the Summary Page
|
Chart |
Description |
|---|---|
| Time Breakdown | Time Breakdown breaks down the total time elapsed within the trace file into time allocated to component activities (CPU, Lock, Network, Control File I/O, and so on). |
| Statement Breakdown | Statement Breakdown breaks down the total time elapsed within the trace file into time allocated to types of SQL statements (SELECT, UPDATE, PL/SQL, EXECUTE, INSERT, COMMIT, and so on). |
| Parsing User |
Parsing User breaks down the total time elapsed within the trace file into time allocated to users who have parsed SQL statements. Note: If the Parsing User chart displays "No data", the user that originally created the trace file may no longer exist on the database, or may have been deleted and re-created. In the second case, the user ID from the trace file will not match the user ID in DBA_TABLES. |
Wait Breakdown Grid
Wait Breakdown shows information about categories of wait events in the selected trace file.
| Column | Description |
|---|---|
|
Top Category |
High-level event categories for waits in the trace file. |
|
Sub Category |
Event categories for waits in the trace file. |
|
Count |
The number of times that a wait event in the specified category has occurred. |
|
Time (ms) |
The amount of time spent on waits in the specified category. |
|
Pct |
The percentage of the total wait time spent on events in the specified category. |
Breakdown Within Wait Grid
Breakdown Within Wait lists all the wait events for the wait category currently selected in the Wait Breakdown table.
| Column | Description |
|---|---|
|
Wait |
For the specified trace file, this column lists every wait in the category currently selected in the Wait Breakdown table. |
|
Object |
The Oracle object to which each wait applies. |
|
Count |
The number of times the specified wait has occurred. |
|
Time (ms) |
The amount of elapsed time spent on the specified wait. |
|
Pct |
The amount of elapsed time spent on the specified wait, measured as a percentage of the total elapsed time. |
