Professional Documents
Culture Documents
(Pics) How Can Trace and Debug Be Turned On For A Concurrent Request? [ID 759389.1]
In this Document
Goal
Solution
Applies to:
Goal
How can the SQL trace and FND Diagnostics be enabled when run a concurrent program?
Solution
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.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010
Page 2 of 7
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.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010
Page 3 of 7
A new screen will appear showing that the rule was created, choose the OK button which closes the window.
4. Do Not submit the concurrent request yet, but instead proceed to locate the maximum log_sequence in the FND_LOG_MESSAGES table where the FND logging will be written.
select max(log_sequence)
from
fnd_log_messages fnd, fnd_user fu
where fnd.user_id = fu.user_id
and fu.user_name = '&USER_NAME'
order by log_sequence desc;
Pass in the USER_NAME which is being used - and is about to replicate the problem.
Example: 81088151
Once it has completed, execute the sql from step 4 again - to locate the new maximum log_sequence.
select max(log_sequence)
from
fnd_log_messages fnd, fnd_user fu
where fnd.user_id = fu.user_id
and fu.user_name = '&USER_NAME'
order by log_sequence desc;
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010
Page 4 of 7
Example: 81088310
6. Pull all data related from the FND_LOG_MESSAGES table - by passing in the two sequence values along with the USER_NAME which submitted the concurrent request.
select fnd.*
from
fnd_log_messages fnd, fnd_user fu
where
fu.user_id = fnd.user_id and
fu.user_name = '&USER_NAME' and
fnd.log_sequence > &SEQUENCE_1 and
fnd.log_sequence < &SEQUENCE_2
order by fnd.log_sequence asc;
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010
Page 5 of 7
7. Export the data to an Excel Spreadsheet, using the export functionality within SQL Developer.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010
Page 6 of 7
8. 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.
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010
Page 7 of 7
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 -
Attachments
Related
Products
Oracle E-Business Suite > Procurement > Procurement > Oracle iProcurement
Keywords
Back to top
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1 10/6/2010