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]
Understanding TKPROF
The TKPROF program can be used to format the contents of the trace file and convert it into a readable output file.
TKPROF can also be used to generate Explain Plan for the queries.
I will create a seperate post to discuss various options available with TKPROF.
Recent Comments
- Ankita T on Oracle Procure to Pay (P2P) and Order To Cash(O2C) Cycles
- Raghu on Oracle E-Business Suite 12 Free Vision Instance
- Danny on Inventory Organization and corresponding Operating Unit, Ledger and Legal Entity
- balram Katre on TDS Setup for suppliers in R12
- Velmurugan on HZ tables in Oracle Receivables
Latest Posts
- R12 – How to Delete Oracle AR TransactionsMarch 22, 2019 - 8:37 pm
- How to Define Custom Key Flexfield (KFF) in R12January 19, 2018 - 5:43 pm
- AutoLock Box Concepts In R12November 10, 2017 - 8:30 am
- R12 – java.sql.SQLException: Invalid column type in OAFSeptember 15, 2017 - 9:39 am
- How to Find Duplicate Row in OAF Page?April 26, 2017 - 5:17 pm
Leave a Reply
Want to join the discussion?Feel free to contribute!