Scribd
Upload
14 views

Concurrent Program Tracing in R12: Source

This document provides instructions for tracing concurrent programs in Oracle Database 12c in three cases: 1) Tracing a concurrent program without bind variables. This involves enabling tracing in the program definition and noting the request ID. 2) Tracing a concurrent program with bind variables and waits. This requires setting specific parameter values before and after running the program while tracing. 3) Enabling tracing for a concurrent request belonging to another user by getting the request ID, process ID, session details, and using DBMS_SUPPORT to start tracing the session.

Uploaded by

Mayank Malhotra
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
14 views

Concurrent Program Tracing in R12: Source

This document provides instructions for tracing concurrent programs in Oracle Database 12c in three cases: 1) Tracing a concurrent program without bind variables. This involves enabling tracing in the program definition and noting the request ID. 2) Tracing a concurrent program with bind variables and waits. This requires setting specific parameter values before and after running the program while tracing. 3) Enabling tracing for a concurrent request belonging to another user by getting the request ID, process ID, session details, and using DBMS_SUPPORT to start tracing the session.

Uploaded by

Mayank Malhotra
Copyright
© © All Rights Reserved
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