Generating a Trace File for Forms
Navigate to Menu – Help > Diagnostics
- Regular
Trace - Trace with
Binds - Trace with
Waits - Trace with
Binds and Waits
Reproduce the performance issue.
– Disable the trace by selecting “No Trace”.
Generating a Trace File for a Concurrent Program
concurrent program definition.
– Reproduce the performance issue.
– Disable the trace option by unchecking the Enable Trace Checkbox in the
concurrent program definition.
mandatory XML tags which should be added by the developers. Without that the
above trace will not work.
Administrator
Security > Profile
User: Enter User name of the user facing the issue.
Query the Profile: FND: Diagnostics
Set the FND : Diagnostics profile to Yes at User level.
under the same user used to set the profile value.
– Navigate to the point immediately before the error is received, if any.
– Click the diagnostic icon at the top of the page. Two options are
displayed:
Set Trace Level
– Click Go.
– A page with a set of options is displayed.
Trace (regular)
Trace with binds
Trace with waits
Trace with binds and waits
– Click Save.
– Return back to the page and reproduce the error, if any.
– Turn off Trace.
Click on option: Set Trace Level
Click Go
Select : Disable Trace
id numbers – there will be more than one and exit the Application.
- Set initialization
parameters for trace file management. - Enable the SQL Trace
facility for the desired session, and run the application. - Run TKPROF to
translate the trace file created in Step 2 into a readable output file.
This step can optionally create a SQL script that can be used to store the
statistics in a database. - Interpret the output
file created in Step 3.Formatting Trace File with TKPROF
Doyen_ora_18190.trc is the name of the raw trace file and trace1.txt is the
name of the TKPROF file.
output_file.txt explain=apps/<apps pw>
sort=‘(prsela,exeela,fchela)
ALTER SESSION SET
EVENTS ‘10046 trace name context forever, level 12’;
— Set the trace
file identifier, to locate the file on the server
ALTER SESSION SET
TRACEFILE_IDENTIFIER = ‘API_TRACE’;
— Execute the API
from the SQL script, in the same session.
EXEC <procedure
name> ;
— Once the API
completes execution, disable trace
ALTER SESSION SET
EVENTS ‘10046 trace name context off’;
— Locate the trace
file based on the tracefile identifier
SELECT VALUE FROM
V$PARAMETER WHERE NAME = ‘user_dump_dest’;
— Generate the
tkprof of the trace file
tkprof
<trace_File>.trc <tkprof>.out sys=no explain=apps/<apps pwd>
oradebug at session Level.
select username, spid from v$process;
process that needs traced.
oradebug setospid 2280
oradebug command below will enable the maximum tracing possible:
oradebug event 10046 trace name context forever, level 12
oradebug event 10046 trace name context off
obtain the file name:
oradebug tracefile_name
readable format.
10046 level 12 trace can be enabled using
(9,29,binds=>true,waits=>true);
can be disabled using
a.SID,a.SERIAL#,b.USERNAME,b.PROGRAM from v$session a , v$process b where
a.PADDR=b.ADDR and b.SPID=’&SPID’
DBMS_SYSTEM.set_sql_trace_in_session(sid=>1390, serial#=>7860,
sql_trace=>TRUE);
Issues with EBusiness Suite [ID 980711.1]
SQL Script Outside of the Applications ? [Video] [ID 869386.1]