metalink上的文章较全的，中文的可参考我的博客EBS开发技术之trace http://blog.csdn.net/cai_xingyun/article/details/17250971

This document provides instructions on how to create and retrieve Forms and Database level SQL trace. The example details below are for receiving processes, but these instructions are also applicable for other forms and concurrent processes.

Please reference Note 299497.1 for instructions on how to gather debug information for receiving processes.

Forms Level Trace

Forms level trace is SQL trace generated before the transaction is saved on a form. It is enabled from the form and captures SQL code related to the execution of the form.  This should be used when the error occurs on the form BEFORE clicking on the save.  Typically these are FRM or APP errors but there could be other varying error messages.

Steps to generate forms level trace:

1. Navigate to the point in the application right before you are experiencing the problem.
2. Turn trace on by: Help > Diagnostics > Trace > Trace with Binds (May require password)
3. A pop-up message with trace file location and name will be displayed. Note the filename and path.
4. Duplicate the error and then stop immediately afterwards.
   Help > Diagnostics > Trace > No Trace
5. Retrieve trace file from the user_dump_dest, which can be located as follows:
   select value from V$PARAMETER where name like 'user%';
6. Run the trace file through tkprof as follows:
   tkprof <filename>.trc <filename>.out explain=<found username/password>
   example: tkprof file1234.trc file1234.out explain=<apps/apps>

Database Level Trace

Database level trace is SQL trace generated after the transaction is saved and receiving transaction processor is processing the transaction. This should be generated when the error occurs AFTER clicking Save to commit the transaction on a receiving form. In Online receiving mode typically "rvtptcontrol failed" error occurs.  For Immediate or Batch receiving modes the error(s) is recorded in the receiving transaction processor concurrent request log file. There are many ways to gather a database trace file for receiving processes.

Methods to Generate Database Level Trace

1. Profile PO: Enable SQL Trace for Receiving Processor

Setting this profile to ‘Yes’ will generate a Event 10046 Level 12 database level trace for the receiving transaction being saved.

Steps to generate trace file:

1. Set profile at user level
   • Bring up the Core application - System Administrator responsibility
   • Go to Profile > System
   • Check off the USER box - and enter the username of the user for whom trace needs to be enabled
   • Search on the following profile option - 'PO: Enable SQL Trace for Receiving Processor'
   • At the user level, set the value of the profile to 'Yes'
2. Once the profile is set, please change responsibilities and directly go and reproduce the problem.
   Error message will be displayed on the form only in online mode. In Immediate / Batch mode, the error will be recorded in the concurrent request log file of Receiving Transaction Processor.
3. Unset the profile before logging off the applications.

Location of the trace file:

1. If the transaction was done in Online mode, then the trace file can be found in user_dump_dest, which can be located as follows:

select value from V$PARAMETER where name like 'user%';

1. If the transaction was done in Immediate or Batch mode, the SQL statement from method below (Enable trace for concurrent program) can be used to retrieve the location and name of the trace file.

2. Enable trace for the concurrent program

This can be used only when saving the transaction in Immediate or Batch mode. This method generates an Event 10046 Level 1 trace only with no bind variables and no waits.

Steps to generate trace file:

1. Enable trace for concurrent program:
   • Bring up the Core application - System Administrator responsibility
   • Goto Concurrent > Program > Define
   • Query the concurrent program (shortname = RVCTP)
   • Check the trace box to enable trace and Save
2. Change responsibilities and directly go and reproduce the problem. In this method, the error message, if any, will not be displayed on the form.
3. Navigate to View > Requests and confirm that Receiving Transaction Processor has completed. The request may or may not end in error. The request log file should show an error. Note the Concurrent Request Id.

Location of the trace file:

The trace file can be located using the SQL below. Use the concurrent request id noted in step 3.

SQL>
prompt
undefine request_id
accept request_id
prompt 'Please enter the concurrent request id of Receiving Transaction Processor:'
promptcolumn traceid format a8
column tracename format a80
column user_concurrent_program_name format a40
column execname format a15
column enable_trace format a12
set lines 80
set pages 22
set head offSELECT 'Request id: '||request_id ,
'Trace id: '||oracle_Process_id,
'Trace Flag: '||req.enable_trace,
'Trace Name:
'||dest.value||'/'||lower(dbnm.value)||'_ora_'||oracle_process_id||'.trc',
'Prog. Name: '||prog.user_concurrent_program_name,
'File Name: '||execname.execution_file_name|| execname.subroutine_name ,
'Status : '||decode(phase_code,'R','Running')
||'-'||decode(status_code,'R','Normal'),
'SID Serial: '||ses.sid||','|| ses.serial#,
'Module : '||ses.module
from fnd_concurrent_requests req, v$session ses, v$process proc,
v$parameter dest, v$parameter dbnm, fnd_concurrent_programs_vl prog,
fnd_executables execname
where req.request_id = &request_id
and req.oracle_process_id=proc.spid(+)
and proc.addr = ses.paddr(+)
and dest.name='user_dump_dest'
and dbnm.name='db_name'
and req.concurrent_program_id = prog.concurrent_program_id
and req.program_application_id = prog.application_id
and prog.application_id = execname.application_id
and prog.executable_id=execname.executable_id;

3. Enable profile ‘Initialization SQL Statement – Custom’

This method should be used when there is requirement to capture trace for processes in related products like INV, OM, WIP etc. initiated by Receiving Transaction Processor. This method enables and Event 10046 Level 12 database trace for the entire session of the user for whom the profile is enabled. The session can be linked to an online Form, a Concurrent Program, or any other piece of code that requires accessing the database.  Hence, this method must be used carefully as it can generate many trace files as user navigates through the applications.

Steps to generate trace file :

1. Enable trace for a specific user:
   • Bring up the Core application - System Administrator responsibility
   • Move to Profile/System
   • Check off the USER box - and enter the username of the user for whom trace needs to be enabled
   • Search on the following profile option - 'Initialization SQL Statement - Custom'
   • Please set this at the user level with the following string:

BEGIN FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER SESSION SET TRACEFILE_IDENTIFIER='||''''||'RCVTRACE' ||''''||' EVENTS ='||''''|| '10046 TRACE NAME CONTEXT FOREVER, LEVEL 12 '||''''); END;

1. • # 1. Cut and paste the above sql statement into the profile value editor. This must be one complete line of text - so may be best to copy the string into notepad prior to putting it into the profile and making sure that there are no special characters in the string.

     # 2. String 'RCVTRACE' in the above statement can be changed to any user-defined value. This is the string that will be included in the filename and will help in identifying all the trace files related to a session.

2. Once the profile is set, please change responsibilities and directly go and reproduce the problem.
   Error message will be displayed on the form only in online mode. In Immediate / Batch mode, the error will be recorded in the concurrent request log file of Receiving Transaction Processor.

Location of the trace file:

1. Locate the trace file using the following sql in sqlplus. The value is the location of the trace file on the database server

select name, value from v$parameter where name like 'user_dump_dest';

Please move to this directory and search for the file having RCVTRACE (or any user-defined value that was specified in the profile value statement) in the filename. There may be more than one trace file created for the session.
Ensure that the profile option is unset before exiting the Application. This is a very important step. If this is not unset, unnecessary trace files will be generated.