Form Level

A form trace is used whenever the poor performance is happening on-line.  

For example, one might use a form trace to trace an inquiry that is taking  a long time to complete 

(i.e..  An ATP inquiry, or an item inquiry).  Before turning trace on at the form level, close the 

application and then re-enter it. This causes any open cursors from your previous session to close.  

Do not turn trace on until just before you are ready to duplicate the problem.

PROCESS

========

• 1. Navigate to the point in the application right before you are experiencing the problem.

  2. Turn trace on by: Help > Diagnostics > Trace > Trace with Binds (May require password)

  3. A pop-up message with trace file location and name will be displayed. Note the filename and path.

  4. Duplicate the error and then stop immediately afterwards.

  5. Help > Diagnostics > Trace > No Trace

  6. Retrieve trace file from the user_dump_dest, which can be located as follows:

  7. select value from V$PARAMETER where name like 'user%';

  8. Run the trace file through tkprof as follows:

  9. tkprof <filename>.trc <filename>.out explain=<found username/password>

  10. example: tkprof file1234.trc file1234.out explain=<apps/apps>