The top of the report says how long the session took, when and where: the total time, the trace period, the count of calls, waits and statements, and the environment the trace itself describes. It is also where you download the report.
What the section shows
The Summary is the first section in the In this report index. Above it, the header has the name of the analyzed file, the Analyzed on line with the analysis date, the size and number of lines of the trace, the Download HTML, Download JSON and Download PDF buttons and the Statements per list field. The section has:
- five numbers: Total time, Period, Database calls, Waits and Distinct statements;
- the Session and environment card, with the database, the instance, the server and the session that the trace header reports;
- the collection card, when several files were analyzed together (collection).
When the analysis finds something that changes how the time should be read, such as waits without tim in an old trace, recursive calls without the level-0 call (a trace cut in the middle) or an analysis limit reached, a warning appears at the top of the report, before the Summary. In a trace with many distinct statements, the warnings say what the analysis started to sum by text shape and what it started to estimate (trace with many statements).
In a deadlock-only trace, the numbers are different: Deadlocks (ORA-00060), Detected at, Sessions involved and Diagnosis (deadlocks).
How to read it
| Number | What it is |
|---|---|
| Total time | The response time (R): from the start of the first call or wait to the last tim in the trace, in seconds, with the same value in ms, s, min or h right below. It is the exact sum of the rows of the profile. In a collection with more than one session, it is the sum of the time of each session. |
| Period | Start and end of the trace on the clock that the trace itself writes in the *** lines with date and time. With the pointer over the number, both instants appear with microseconds and time zone. Without those lines, not reported appears. |
| Database calls | All PARSE, EXEC, FETCH, CLOSE and other calls, at any depth. Below, how many are level-0 calls, the ones the application requested; the others are recursive SQL. |
| Waits | How many WAIT lines the trace has. Below, the seconds of waiting between calls, such as SQL*Net message from client. |
| Distinct statements | How many different SQL and PL/SQL statements the trace has, by sql_id or, without it, by hash value. Statements that differ only in their literals count one by one, even when the lists show them in a single row. When the analysis had to estimate the count, the number appears as about N. Below, the commits and rollbacks, counted in the XCTEND lines. |
| Field | Where it comes from in the trace |
|---|---|
| Database | The Oracle Database line of the header and the Version line. |
| Instance | Instance name. |
| Server | Node name, with System name, Machine and Storage when present. |
| Session | SID and serial from *** SESSION ID, and the pid from Unix process pid. |
| Service | *** SERVICE NAME. |
| Module and Action | The distinct values of *** MODULE NAME and *** ACTION NAME, in the order they appear in the trace. |
| Client ID and Driver | *** CLIENT ID and *** CLIENT DRIVER. |
| Container (PDB) | *** CONTAINER ID. |
| Time unit | microseconds, or centiseconds (old trace) in Oracle 7 and 8 traces. |
| File on server | The path of the trace on the database server, from the Trace file line. It does not appear in a collection. |
A field the trace does not have does not appear. Check in the card that the trace is from the right session and database before drawing conclusions.
Download the report
- Download HTML saves the file
<trace name>-relatorio.html, which opens in any browser, without the console: the styles are embedded and the cards for components and plan operations open the same way. The file opens with the summary and the lists; the detail of a statement or an object is built only when you click it, and Back to the report takes you back. In the index, Find a statement by sql_id lists the detailed statements whosesql_idstarts with what you type. The object detail has the type, the wait and where the object appears in the trace; the ready-made queries are only in the console. To navigate, the file needs JavaScript. - Download PDF opens the full report in a new tab, with the detail of every statement and object at the end, and calls the browser's print dialog: choose to save as PDF. In the downloaded HTML, the Download PDF button does the same with the file.
- Download JSON saves
<trace name>-resultado.json, the full analysis result, to take to another tool. Through the API, you download the same HTML and a JSON with the report sections.
The statement lists show 10 statements each. To change that, type another number in Statements per list (from 1 to 300) or check all, and click Apply. The choice applies to the lists on the page and to the downloaded HTML and PDF, which say at the top how many statements per list they have.
With Report privacy turned on in My account, the page, the downloaded HTML and JSON, the API and the app show the SQL with the quoted text, the numbers used as values, or both, replaced by ***, according to the checked options. The stored analysis does not change: uncheck the options to see the original SQL (hidden literals).
Delete the analysis
Deletion is on the Analyses page, under History, and not in the report.
- Click Analyses in the path at the top of the report.
- To delete one analysis, click Delete on its row.
- To delete several, check the boxes on their rows, or Select all, click Delete selected and confirm.
Result: the page shows Analysis deleted. or how many analyses were deleted, and the report address starts to respond Analysis not found.
Delete on the row deletes right away, without asking for confirmation, and cannot be undone. The trace was already deleted at the end of the analysis: to get the report again, upload the file again. The HTML and JSON you downloaded stay with you.
Without deletion, the report disappears on its own when the retention period expires (retention and privacy).
When it is a concern
- The Period starts well before or ends well after the operation you wanted to measure: part of the total time is from before or after it.
- The Total time is much shorter than the delay the user felt: the trace caught only part of the operation, or another session.
- Database calls far above the level-0 ones: there is a lot of recursive SQL, from functions, triggers or data dictionary queries.
- Waits with many seconds between calls: the time may be outside the database (session waiting for the application).
- Rollbacks above zero: check whether the undone work was expected (rollback).
- A warning at the top of the report: read it before the rest, because it says what the analysis could not measure.
Where to go next
- Summary of the sample report: total time of 0.007 s (7.0 ms), 6 database calls, 4 of them at level 0, 4 waits and 2 distinct statements.
- Diagnosis, the next section of the report.
- Response time profile, which splits the total time into parts.