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:
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.
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).
The function can only work if a process server is installed and is active on the database machine.
For the configurations where the application server is situated in a Unix machine, the users that want to launch the Oracle log file must be in the DBAgroup
When the function is used, a screen is used to enter a group of options :
It is possible to choose whether to use the next three options or not
AGGREGATE | Indicates if identical records must be grouped in a single SQL request or left independent. |
WAITS | Indicates whether the summaries must be recorded for the suspended events. This option is only available from version 9i. |
SYS | Indicates if it is necessary to display the recursive SQL executed by SYS |
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):
prscnt | Number of analysis calls (PARSE) |
prscpu | CPU time consumed for the analysis |
prsela | Time passed for the analysis |
prsdsk | Number of reads to the disk |
prsqry | Number of buffers for a coherent read during analysis |
prscu | Number of buffers during the parse phase |
prsmis | Number of cache "library" failures during the analysis |
execnt | Number of executions called |
execpu | CPU time consumed by the execution |
exeela | Time passed during the execution |
exedsk | Number of reads on the disk during the execution |
exeqry | Number of buffers for a coherent read during execution |
execu | Number or buffers during the execution phase |
exerow | Number of lines processed during the execution |
exemis | Number of failures in the "library" cache during execution |
fchcnt | Number of extraction calls (FECTH) |
fchcpu | CPU time consumed by the extraction |
fchela | Time passed for the extraction |
fchdsk | Number of reads to the disk during FETCH |
fchqry | Number of buffers for a coherent read during extraction |
fchcu | Number of buffers for the read during the extraction |
fchrow | Number of lines processed during the extraction |
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.
Count | Number of analyses, executions, and extractions carried out. |
CPU | Total CPU time, expressed in seconds used by the analysis, execution and extraction phases. |
Elapsed | 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). |
Disk | Total number of data blocks physically read in the data files for the analysis, execution or extraction phases. |
Query | Total number of buffers extracted in coherent mode for all the phases. |
Current | Total number of buffers extracted in the current mode for all the phases. |
Rows | Total number of processed lines (but this does not concern sub-requests) |
In addition to the generic error messages, the following messages can appear during the entry :
The access to the database machine is not possible, there is no process server or it is not on-line.
The directory indicated as the log file directory is not accessible.
