Oracle requests log 


This tool is accessible from any screen in the software once the database used is Oracle™, using the Tools menu located at the top of the screen and which contains the two following choices:

Oracle log file activation

Via the Oracle SQL_TRACE there is the possibility to activate the recording of the SQL commands executed in a file that can then be analyzed.

Log file de-activation

This function launches a processing via the Oracle tool TKPROF that processes the log file obtained by activation and then displays the result. This makes it possible to view all the SQL commands executed during the activation period.



The user must be authorized to use the debugger (DBG parameter).

Technical constraint

The function can only work if a process server is installed and is active on the database machine.

User Interface

When the function is used, a screen is used to enter a group of options :

Recover results

It is possible to choose whether to use the next three options or not


Indicates if identical records must be grouped in a single SQL request or left independent.


Indicates whether the summaries must be recorded for the suspended events. This option is only available from version 9i.


Indicates if it is necessary to display the recursive SQL executed by SYS

Sort options

By default the SQL commands are detailed in chronological order but it is possible to specify the sort options.

Several sort options are suggested and the first is the order corresponding to the highest cost according to the sort requested.

The user can also choose the sort options they require using the "Advanced sort setup". The corresponding window will be used to choose all the possible options among the following (listed by request processing phase):


Number of analysis calls (PARSE)


CPU time consumed for the analysis


Time passed for the analysis


Number of reads to the disk


Number of buffers for a coherent read during analysis


Number of buffers during the parse phase


Number of cache "library" failures during the analysis


Number of executions called


CPU time consumed by the execution


Time passed during the execution


Number of reads on the disk during the execution


Number of buffers for a coherent read during execution


Number or buffers during the execution phase


Number of lines processed during the execution


Number of failures in the "library" cache during execution


Number of extraction calls (FECTH)


CPU time consumed by the extraction


Time passed for the extraction


Number of reads to the disk during FETCH


Number of buffers for a coherent read during extraction


Number of buffers for the read during the extraction


Number of lines processed during the extraction

Presentation of the results

The user can choose to list only the first n SQL commands returned.

When a sort has been chosen, it will obtain the first n SQL orders that correspond to the highest level in this sort.

Explanation of the result of tkprof


Number of analyses, executions, and extractions carried out.
(Check the presence of a value grater than 0 before interpreting the other columns). Unless AGGREGATE=no , TKPROF groups the identical SQL instructions.


Total CPU time, expressed in seconds used by the analysis, execution and extraction phases.


Total time, in seconds, given to all the analysis, execution or extraction calls (here the waits are added and therefore this time corresponds both to the Oracle operations as well as the CPU operations).
It is necessary to verify that there is no notable difference between the CPU and Elapsed time.


Total number of data blocks physically read in the data files for the analysis, execution or extraction phases.


Total number of buffers extracted in coherent mode for all the phases.


Total number of buffers extracted in the current mode for all the phases.


Total number of processed lines (but this does not concern sub-requests)
- Select: this number is found in the column Fetch
- Insert , Update and Delete: this number is found in the Execute column.


In addition to the generic error messages, the following messages can appear during the entry :

"Error during the access to the database server"

The access to the database machine is not possible, there is no process server or it is not on-line.

"Access error for the database log file directory"

The directory indicated as the log file directory is not accessible.