How Can Trace and Debug Be Turned On For A Concurrent Request (Doc ID 759389.1)
How Can Trace and Debug Be Turned On For A Concurrent Request (Doc ID 759389.1)
1 1 of 10
How Can Trace and Debug Be Turned On For A Concurrent Request? (Doc ID 759389.1)
In this Document
Goal
Solution
References
APPLIES TO:
GOAL
How can the SQL trace and FND Diagnostics be enabled when run a concurrent program?
SOLUTION
Attention: If using Release 12 - the following patch is required for the trace to work properly using the steps below. Patch 8743459
The following steps outline how to enable a sql level trace and FND logging when submitting a concurrent program.
1. The following profile options will need to be set in order to enable the Debug Options button in the Concurrent Request Submission
form: Profile - Concurrent: Allow Debugging
2. Next, proceed to the Concurrent Request Submission form to submit the concurrent program in question.
- Select the Single Request - and input all parameters
Rather than submitting the request, choose the 'Debug Options' button now enabled in the submission form.
Rather than submitting the request, choose the 'Debug Options' button now enabled in the submission form.
3. In the web based form that opens, choose the options as seen below to enable trace and FND logging.
Upon selecting the options, choose the OK button off to the right.
A new screen will appear showing that the rule was created, choose the OK button which closes the window.
Pull the FND Logging using SQL Developer using the following SQL:
SELECT log.*
FROM fnd_log_messages log,
fnd_log_transaction_context con
WHERE con.transaction_id = &requestid
AND con.transaction_type = 'REQUEST'
AND con.transaction_context_id = log.transaction_context_id
ORDER BY log.log_sequence;
5. Export the data to an Excel Spreadsheet, using the export functionality within SQL Developer.
6. To locate the trace file, utilize the following sql to confirm the trace file location on the database server.
Move to the directory given on the database server, and list the trace files based on the Concurrent Request ID which was submitted.
The trace filename will contain the USER_NAME which submitted the concurrent request along with the letters CR - as can be seen
above.
PERFORMANCE ISSUES:
If the issue is for a performance problem, please use the following tkprof syntax so that the highest cost statement is seen first in the
tkprof output -