Did you know that you can enable trace dynamically when submitting a concurrent request?

You can get more options and dynamically enable trace during a program or report submission. A trace file may be required while debugging an issue to show the SQL run and other important details about a program or report. A common way to enable trace is via system administration setup with the “Enable Trace” Checkbox on the concurrent program setup under System Admin > Concurrent > Program > Define.

 

This method however does not give binds or waits. Binds are used to see variables used in SQL queries. The waits are used for performance validations. Also, the option is not dynamic and would impact everyone submitting the program or report, not just the user who wants the information. A trace can be helpful but creating a trace when not required can create large unnecessary files as well as slow down the performance of a program. It would help to have the option on report/program submission to enable trace and it is available.

To enable this feature, you first must be sure to have the profile enabled. Again, tracing is not something you should do unless debugging an issue so you want to be careful who has this option to avoid system performance issues and large unnecessary trace files. Always consult with your system administrator and test thoroughly before making any application setup changes. The profile is “Concurrent: Allow Debugging”. If set to Yes, the application enables a “Debug Options” button while submitting concurrent requests.

When submitting the concurrent program choose the “Debug Options” button and set trace.

a. Navigate to View > Requests > Submit request

b. Enter the request Name.

c. Choose Debug Options (Button)

d. Set the trace values and press Ok (Button):

* SQL Trace (Checkbox) = Yes

e. You would get various options. For example, you might choose to enable trace with binds:

* Debug Option Value (poplist) = SQL Trace with Binds and Waits

f. Submit the request

g. Retrieve the log file and the related SQL Trace.

 

For more Common Tracing Techniques in Oracle E-Business Applications, please refer to Doc ID 296559.1