Steps for Forms Based Applications-Tuning
1. Log in to the environment from which you want to trace.
2. Set the value for profile option "Utilities:Diagnostics" to "Yes" at user-level for your application account.
3. Choose your responsibility, and navigate to the starting point of the form when you want to begin tracing.
4. Turn on Tracing by using the menu option: Home > Diagnostics > Trace > Trace with waits.
5. A popup note with the trace file name and location is displayed. Note the trace file name. The location will be on the database server.
6. Proceed with the application steps that need to be traced. Once you finish tracing, exit the application.
7. Retrieve the raw trace file using the file name from Step 5.
8. Format the raw trace file with TKPROF.
Tip: In most cases, it is good enough to review the TKPROF file. But sometimes RPC
(RemoteProcessCall) or some Error causes the issue. This information is not translated into the TKPROF output. In general, when RPCs take a long time, the TKPROF file points to a high amount of “sql*net message from the client” waits time. So you need to review the raw trace file also.
If you suspect RPC performance, you may check the trace file with RPC.
$grep -n RPC [trace file name].trc > rpc.txt
C:\trace\findstr -n RPC [trace file name].trc > rpc.txt
And review the output file, rpc.txt
If you find some oracle error in the screen or log file, you may check the trace file
$grep -n "err=" [trace file name].trc > err.txt
c:\trace\findstr -n "err=" [trace file name].trc > err.t