How to enable / generate trace for a concurrent program

Posted on July 28, 2008. Filed under: DBA/Admin Tips, Diagnostics, R12 | Tags: , , |

Login as Sysadmin -> System Administrator -> Concurrent : Program -> Define
Press F11 -> Enter the COncurrent Program Name (Eg. Active Users) -> Press Ctrl + F11
Enable the check box “Enable Trace” above “Copy To” button.
Click on Save.
Close the window.
Select Requests -> Run
Submit the concurrent request.

After completion or during execution of the request, you should see a trace file generated on the database server under udump directory.

SQL to identify the trace file

select oracle_process_id from fnd_concurrent_requests where request_id=[request_id];

DB Node
cd $ORACLE_HOME/admin/[SID]_[hostname]/udump
ls -latr *[oracle_process_id]*.*

P.S: Dont forget to disable the trace 🙂



Make a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

4 Responses to “How to enable / generate trace for a concurrent program”

RSS Feed for OraclePitStop – Lets share some knowledge Comments RSS Feed

[…] get more information, i enabled trace for Active users concurrent program (How to enable trace)and resubmitted it. Strange, it didnt even generate a trace file, but a session had been […]

Its Really good and simple

[…] Tips, Diagnostics, R12, TroubleShooting | Tags: bind, concurrent program, trace | In this link, we had mentioned about tracing a concurrent program, but the drawback of this method is it doesnt […]

Where's The Comment Form?

Liked it here?
Why not try sites on the blogroll...

%d bloggers like this: