View Suresh Vaishya's profile
If your program is taking time to complete, then the best way to know what is causing the problem is by creating a trace file.
Navigation:
System Administrator(R) --> Concurrent --> Program --> Define
Query for the concurrent program and check enable trace button.
Now when the concurrent program is executed the trace file is created in the udump directory. The path of udump directory can be found by executing following query.
select * from v$parameter
where name like '%user_dump_dest%'
The trace file can be converted to a readable format by running a tkprof command over the trace file.
Syntax:
tkprof [trace_file_name] [new_file_name]
Click for more info on TKPROF
3 Comments:
How do you know which trace file that was generated if the concurrent Executable Method is Host, and the executable is a shell script calling another .sql file ?
thx,
SRM
when u enable regular trace from
(navigation - Help->diagnostics->trace->regular trace) it will show you a path (udump)along with the file name.
thanks,
This post tells you how you can create trace file for concurrent program. The steps are well explained with the help of screenshot. The syntax is easy to remember. I think you don't need to do too much effort for understanding this topic. Thanks.
Post a Comment