Trace with no time span

Without time, there is no profile: the response time comes from the distance between the first and the last tim in the trace. This finding warns that the file has 10046 lines, but none that marks a time span.

Symptoms

In the Diagnosis, only the finding Trace with no time span (TRACE_VAZIO) appears, with the text There are no calls or waits with tim; there is no response time to analyze. The severity is info, and the finding has no link. In the Summary, the Total time is zero.

The finding appears when the file was accepted as a 10046 trace, but the response time is zero: no call (PARSE, EXEC, FETCH and the others), wait or end of transaction with tim opens a time span. If the file has a deadlock, the deadlock findings appear instead of this one.

A file without any 10046 line does not even reach the report. The analysis ends with the error the file does not look like an Oracle trace (event 10046), or with the file type when the console recognizes it: optimizer trace (10053), incident trace, state dump or alert log (rejected files).

Cause

• The file is a piece of the trace. The session wrote to more than one file (a change of tracefile_identifier, *** TRACE CONTINUES IN FILE marks), or the file was cut or filtered before the upload, and the excerpt left has no call or wait with tim.
• Tracing was turned off right after it was turned on, before the session made a call with a duration.
• The file belongs to another session or another process, and not to the operation.

Resolution

1. Check what the file contains by counting the calls and the waits:

   grep -c -E "^(PARSE|EXEC|FETCH) #" arquivo.trc
   grep -c "^WAIT #" arquivo.trc

   Result: zero calls and zero waits confirm that the file does not cover the operation.

2. Find the right file of the session (find the trace file).
3. If the session wrote to more than one file, upload them all together, so that the console analyzes them as a collection (analyze several files together).
4. If the right file also has no calls, generate the trace again: turn it on before the operation starts, run the whole operation and turn it off after the end (turn on tracing with DBMS_MONITOR), at a level with waits (10046 levels).

How to confirm

Upload the new file. The Summary shows a Total time above zero and the Period of the operation, the Response time profile has rows, and the finding disappears from the Diagnosis.

In the report

• Summary: Total time, Period, Database calls and Waits. The sample shows what a trace with time looks like (summary).
• Warnings at the top of the report: they say, for example, when there are recursive calls without the matching level-0 call, a sign of a trace started or cut in the middle of a call.
• Response time profile: in a trace with time, the rows add up to the Total time (profile).
• Collection: with several files from the same session, the report shows the files and the segments of each one (collection).