Obtaining Forms Runtime Diagnostics (FRD) In Oracle Applications 11i

1. Set the user value for profile option 'ICX: Forms Launcher' to be
'http://hostname.domain:port/forms/frmservice?record=forms'

2. By default, this will enable tracing for errors only. As an optional step, you can enable different trace options (e.g. user actions, user-exit events, dbsql events, network events) by setting a trace group in file $ORA_CONFIG_HOME/10.1.2/forms/server/ftrace.cfg

3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace.

4. Locate the file in the directory set by variable FORMS_TRACE_DIR. Note: by default, this directory is named forms_.trc, where is the process identifier.Related

Tracing in 11.5.10

1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value
e.g. copy value of ICX: Forms Launcher for the site Test115 'http://testserver.oracle.com:8005/dev60cgi/f60cgi' to be the value for the user.

2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD
e.g. update the value of ICX: Forms Launcher for the user to be 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log

3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace.

4. Locate the file in the directory set by variable $FORMS60_TRACE_PATH. Note: the default directory for $FORMS60_TRACE_PATH is $ORACLE_HOME/forms60/log.

FRD Tracing in 11.5.x to 11.5.9

This method enables users to run FRD tracing through the Personal Home Page by setting debugging to true using the profile option 'ICX: Forms Launcher'.
When accessing Applications through the Personal Home Page (PHP), there is no way to pass command line parameters such as config=debug and record=all for the duration of a single session.
For example, you cannot add these variables to the PHP connect string

http://testserver.oracle.com/OA_HTML/US/ICXINDEX_test115.htm.

The advantages of using the profile option 'ICX: Forms Launcher' are that you can easily trace the activities of multiple users and assign different log file names.
With Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter

$FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.

Steps:

To start tracing in this way, modify Profile Option 'ICX: Forms Launcher' at USER level to include the Forms parameters required for FRD logging:

1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value

e.g. copy value of ICX: Forms Launcher for the site Test115

'http://testserver.oracle.com:8005/dev60cgi/f60cgi'
to be the value for the user.

2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD
e.g. update the value of ICX: Forms Launcher for the user to be

'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=/tmp/username_frd.log

3. Save this change at the USER level, and the next time you access the test115 database through PHP, the Forms variables will be enabled.

Old option: adhoc FRD tracing :

The steps below show how to create an FRD trace file quickly. This is not a supported or preferred method of tracing, however, it may be useful to use this method for adhoc and basic troubleshooting purposes.Note after Oracle Developer Forms patch 16 and higher, users cannot create adhoc FRD trace files in any directory. The trace files are either created in the directory set by parameter
$FORMS60_TRACE_PATH or they are created in 8.0.6 $ORACLE_HOME/forms60/log directory.

1. Logon to Applications 11i and append the following text to the URL: record=all&log=/tmp/username_frd.log
a) Example on Unix:
A typical URL to logon to 11i applications: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?'
The URL with FRD trace enabled: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record= all&log=/tmp/username_frd.log'
b) Example on Windows platforms:
A typical URL to logon to 11i applications: 'http://testserver.oracle.com:8005/dev60cgi/ifcgi60.exe'
The URL with FRD trace enabled: 'http://testserver.oracle.com:8005/dev60cgi/ifcgi60.exe?record= all&log=c:\temp\username_frd.log'

2. Reproduce the steps that you wish to trace in Applications.

3. Exit Applications and logout.

4. Locate the trace file at the server. In the above example, the forms runtime diagnostic trace information will be created to file form1.frd in /tmp or in c:\temp directory depending on the platform on which Applications is installed.