Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
The main use of enabling trace for a concurrent program comes during performance tuning.
By examining a trace file, we come to know which query/queries is/are taking the longest
time to execute, there by letting us to concentrate on tuning them in order to improve the
overall performance of the program.
The following is an illustration of how to Enable and View a trace file for a Concurrent
Program.
27 Apr. 15
Check the Enable Trace Check box. After that go to that particular Responsibility and run the
Concurrent Program.
27 Apr. 15
The trace file by default is post fixed with oracle Process_id which helps us to identify which
trace file belongs to which concurrent request. The below SQL Query returns the process_id
of the concurrent request:
The path to the trace file can be found by using the below query:
1 SELECT * FROM V$PARAMETER WHERE NAME='user_dump_dest'
27 Apr. 15
The Trace File generated will not be in the readable format. We have to use TKPROF utility
to convert the file into a readable format.
27 Apr. 15
27 Apr. 15
27 Apr. 15