How to collect the Log, SQLtrace, and FRDlog of each EBS Module

The EBS modules I usually use are as follows: PO, INV, and OM. therefore, you often need to collect related log information. if an error is reported on the interface, you can easily see the code execution error in the log. this blog summarizes the methods for collecting the above logs, and the OM mode, which is the main record of sqltrace and frdlog.1.OMlog.

The EBS modules I usually use are as follows: PO, INV, and OM. therefore, you often need to collect related log information. if an error is reported on the interface, you can easily see the code execution error in the log. this blog summarizes the methods for collecting the preceding logs, SQL trace and frd log. 1. OM log, which records the OM Module

The EBS modules I usually use are as follows: PO, INV, and OM. therefore, you often need to collect related log information. if an error is reported on the interface, you can easily see the code execution error in the log.

This blog summarizes the methods for collecting the preceding logs, SQL trace and frd log.

1. OM log

This mainly records the log of the OM module. The code file of the OM module starts with OE, and the file contains the log statement: oe_debug_pub.add (). The content written in this statement will be written to the log.

Set profile

OM: Debug Level = 5

OM: Debug Log Directory =/usr/tmp

The default log directory is/dbfiles/applcsf/log, but this directory does not exist and cannot be created... we only improved to the/usr/tmp directory. in fact, you only need to select value from v $ parameter where name = 'utl _ file_dir 'to get the directory.

Open the Sales Order form and choose menu> Tools> debug.

A window will pop up: <喎?http: www.2cto.com kf ware vc " target="_blank" class="keylink"> VcD4KPHA + pgltzybzcm9 "http://www.2cto.com/uploadfile/Collfiles/20140522/2014052209120425.jpg" alt = "\">

Then you can find the log in the/usr/tmp directory.

2. INV log

Set profile

3. RCV log -- in patch 9184617: R12.PO. after A, the RCV log is printed in the INV log. therefore, if you set the profile of INV and rcv for R12, you can get the RCV log in INV log.

4. SQL trace

You can set it on the form interface, but this can only collect the SQL statements on the form interface. The SQL statements used for subsequent concurrent calls cannot be collected.

To collect all SQL traces, set the following profile

"Initialization SQL Statement-Custom" = "Begin fnd_ctl.fnd_sess_ctl (" ', '', 'true', 'true', 'log ', 'alter session set TRACEFILE_IDENTIFIER = '| ''' | 'file _ name' | ''' | 'events =' | ''' | '10046 trace name context forever, LEVEL 12' | '''); End ;"

The SQL trace file is in the SELECT value FROM v $ parameter WHERE name = 'user _ dump_dest 'directory;

5. FRD log

FRD log can record the trigger executed on the form interface. The collection method is to set the profile:

"ICX: Forms Launcher" = "http://hostname.domain: port/forms/frmservlet? Record = collect"

Above hostname, domain, port should be modified according to own instance. Like mine: http://bej301441.cn.oracle.com: 8001/forms/frmservlet? Record = collect

After the logout is saved, login is displayed. A window is displayed, indicating that the FRD log has been opened.