EBS R12 Concurrent program tracing
0 likes674 views
1. This document outlines three cases for tracing concurrent programs in Oracle Database 12c. 2. The first case describes how to trace a concurrent program without bind variables. The second case shows how to trace a program with bind variables and waits, including setting parameters to enable this. 3. The third case explains how to enable tracing for a concurrent request when you do not have privileges to run the request directly, by getting the session ID and serial number and using DBMS_SUPPORT to start the trace.
EBS R12 Concurrent program tracing
- 1. Source –http://appsdba.info 1 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>;
- 2. Source –http://appsdba.info 2 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.