Scribd
Upload
32 views

Concurrent Program Tracing

This document describes three cases for tracing concurrent programs in Oracle R12. Case 1 explains how to enable tracing for a concurrent program without bind variables by checking the trace box when defining the program and executing it to get the request ID. Case 2 describes how to trace a program with bind variables and waits by altering system parameters, executing the program to get the request ID, and then turning tracing off and resetting parameters. Case 3 explains how to enable tracing for a concurrent request you do not have privileges for by getting the request ID, Oracle process ID, session details, and executing DBMS_SUPPORT.START_TRACE_IN_SESSION to enable the trace.

Uploaded by

Abdul Nabi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
32 views

Concurrent Program Tracing

This document describes three cases for tracing concurrent programs in Oracle R12. Case 1 explains how to enable tracing for a concurrent program without bind variables by checking the trace box when defining the program and executing it to get the request ID. Case 2 describes how to trace a program with bind variables and waits by altering system parameters, executing the program to get the request ID, and then turning tracing off and resetting parameters. Case 3 explains how to enable tracing for a concurrent request you do not have privileges for by getting the request ID, Oracle process ID, session details, and executing DBMS_SUPPORT.START_TRACE_IN_SESSION to enable the trace.

Uploaded by

Abdul Nabi
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Source http://appsdba.

info

Concurrent Program Tracing in R12


CASE 1 : Concurrent Program Tracing without bind variables 1) Follow the following navigation to enable logging for conc prog Goto Sysadmin > Concurrent > Program > Define Query the concurrent program Check the trace box to enable trace 2) Execute the concurrent program and note down the request id CASE 2: Concurrent Program Tracing with bind variables and waits 1) Note down the following values
SELECT value FROM v$parameter WHERE name = max_dump_file_size; SELECT value FROM v$parameter WHERE name = timed_statistics;

2) Execute the following commands as sysdba


ALTER SYSTEM SET max_dump_file_size = unlimited; ALTER SYSTEM SET timed_statistics = true; ALTER SYSTEM SET EVENTS 10046 trace name context forever, level 12;

3) Execute the concurrent program and note down the request id 4) Turn off tracing the reset the values
ALTER SYSTEM SET EVENTS 10046 trace name context off; ALTER SYSTEM SET max_dump_file_size = <value from step 1>; ALTER SYSTEM SET timed_statistics = <value from step 1>;

Source http://appsdba.info

CASE 3: Enabling the trace for a concurrent request for which you donot have privileges to run the concurrent Request. 1) Ask the person who is privileged to run the concurrent program and get the request id xxxxx 2) Get the oracle_process_id for that concurrent request.
SQL>select request_id,oracle_process_id from fnd_concurrent_requests where request_id in (xxxxxxx);

3) Now get the session details ( SID and Serial ) using value obtained from step 2
col SID/SERIAL format a10 col username format a15 col osuser format a15 col program format a40 select s.sid || , || s.serial# SID/SERIAL , s.username , s.osuser , s.status , p.spid OS PID , s.inst_id , s.module from sys.gv_$session s , sys.gv_$process p Where s.paddr = p.addr and s.inst_id = p.inst_id and p.spid=&value_from_step2 order by to_number(p.spid);

4) Execute the following command to enable the trace :


SQL> EXECUTE dbms_support.start_trace_in_session (&SID,&SERIAL,binds=>true,waits=>true);

5) Collect the trace from udump location and investigate the issue. We can follow the Metalink Note: 296559.1 to know more about tracing.
2

You might also like