How Can Trace and Debug Be Turned on for a Concurrent Request 7593891

8/8/2019 How Can Trace and Debug Be Turned on for a Concurrent Request 7593891

1/7

this DocumentGoalSolution

pplies to:

rocurement - Version: 11.5.1 to 12.0formation in this document applies to any platform.

oal

ow can the SQL trace and FND Diagnostics be enabled when run a concurrent program?

olution

he following steps outline how to enable a sql level trace and FND logging when submitting a concurrent program.

hese steps utilize SQL Developer.QL Developer can be downloaded from the following location for free and is recommended:tp://www.oracle.com/technology/software/products/sql/index.html

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

Next, proceed to the Concurrent Request Submission form to submit the concurrent program in question.Select the Single Request - and input all parameters

ather than submitting the request, choose the 'Debug Options' button now enabled in the submission form.

Pics) How Can Trace and Debug Be Turned On For A Concurrent Request? [ID 759389.1]

Modified05-APR-2010 Type HOWTO Status PUBLISHED

Page 1 of 7

10/6/2010ttps://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWTO&id=759389.1


2/7

ather than submitting the request, choose the 'Debug Options' button now enabled in the submission form.

In the web based form that opens, choose the options as seen below to enable trace and FND logging.

pon selecting the options, choose the OK button off to the right.

Page 2 of 7



3/7

new screen will appear showing that the rule was created, choose the OK button which closes the window.

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.

elect max(log_sequence)omd_log_messages fnd, fnd_user fuhere fnd.user_id = fu.user_idnd fu.user_name = '&USER_NAME'der by log_sequence desc;

ass in the USER_NAME which is being used - and is about to replicate the problem.

ake note of the sequence number that is returned.

xample: 81088151

Proceed now to submit the concurrent request.

nce it has completed, execute the sql from step 4 again - to locate the new maximum log_sequence.

elect max(log_sequence)omd_log_messages fnd, fnd_user fuhere fnd.user_id = fu.user_idnd fu.user_name = '&USER_NAME'der by log_sequence desc;

Page 3 of 7



4/7

xample: 81088310

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.

xecute the following sql statement:

elect fnd.*omd_log_messages fnd, fnd_user fuhere.user_id = fnd.user_id and.user_name = '&USER_NAME' andd.log_sequence > &SEQUENCE_1 andd.log_sequence < &SEQUENCE_2der by fnd.log_sequence asc;

Page 4 of 7



5/7

Export the data to an Excel Spreadsheet, using the export functionality within SQL Developer.

Page 5 of 7



6/7

To locate the trace file, utilize the following sql to confirm the trace file location on the database server.

elect name, valueom v$parameterhere name like 'user_dump_dest';

ove to the directory given on the database server, and list the trace files based on the Concurrent Request ID which was submitted.

Page 6 of 7



7/7

he trace filename will contain the USER_NAME which submitted the concurrent request along with the letters CR - as can be seen above.

pload both the raw and tkprof trace files.kprof .trc .out explain=xample: tkprof sox_ora_7095_CBAKER_CR3514556.trc 7095.out explain=

ERFORMANCE ISSUES: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 -

kprof .trc .out explain=apps/apps sys=no sort='prsela, exeela, fchela'xample: tkprof sox_ora_7095_CBAKER_CR3514556.trc 7095.out explain= sys=no sort='prsela, exeela, fchela'

Back to top

Attachments

image11.jpg (69.88 KB)














Related

Products

Oracle E-Business Suite > Procurement > Procurement > Oracle iProcurement

Keywords

V$PARAMETER; FND_LOG_MESSAGES; FND_USER; USER_DUMP_DEST; RAW; PERFORMANCE; TRACE; EXCEL; V$PARAMETER

Page 7 of 7

How Can Trace and Debug Be Turned on for a Concurrent Request 7593891

Documents

Transcript of How Can Trace and Debug Be Turned on for a Concurrent Request 7593891