1. Navigate to
Profile/System and query the following profile name:
a.
Concurrent: Allow
Debugging
b. Set this profile to
Yes
2. Next, move to the
appropriate responsibility from which you are running the concurrent request.
a. If using Purchasing
Super User responsibility
b. Choose Reports/Run
c. Enter the request
name
d. Enter any
parameters required to run the request
e. A new button will
be shown - entitled 'Debug Options' click this button and a web based
form will open.
f. In the new form,
choose the SQL Trace option and set this to Trace with Binds and Waits
g. Hit the OK button
h. A message will
appear 'Debug Rule has been created successfully' Choose OK and
the web form will close
i. Submit the request and Take note of the Concurrent Request ID
3. In sqlplus -
execute the following statement -
a. select name, value from v$parameter where name like 'user_dump_dest';
b. Take note of the
value output - this is the location on the database server where the trace
files are located. The trace file name will have the concurrent request id along
with the username for the user that submitted the request.
4. How to get the TKPROF from the trace file
a. TKPROF Function:
TKPROF
accepts the raw trace file as input, and produces a formatted output file that
is most readable than raw trace file.
b. Generate TKPROF
report: At the command prompt, change your
directory to the directory where the trace files are located (or,
alternatively, copy the trace files to a location of your choice, and change
your command prompt directory to that directory).
c. Execute command
like the following:
tkprof
<trace file> <output file> explain=userid/pwd@database
Example:
tkprof
file1234.trc file1234.out explain=<apps/apps>
5. After collecting the trace file and TKPROF, please send it
to Support engineer to help you identify the problem with the concurrent
process.
