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.

How to run Forms Runtime Diagnostics (FRD) in 10gR2 Forms.

FRD is a runtime event-based logging system intended to aid in the debugging of Forms
applications. FRD is enabled at runtime on a user by user basis. When a form is run with
FRD enabled, a combination of external user-application interactions and internal Forms
processing events are written in chronological order to a log on the file system. These events
can then be analyzed by both application developers, and Oracle support staff. FRD is not
intended to be used as a performance benchmarking tool or as a mechanism for gauging code
coverage.
FRD generates extensive output useful for analysis and debugging, and it is therefore
recommended FRD be utilized as a logging mechanism only when specific issues are
encountered.

To implement FRD do the following:

In the $ORACLE_HOME/forms/server/default.env (or whatever env file you are using), add the environment variable FORMS_TRACE_DIR specifying a physical directory on the Application Server machine. The FRD log file will be written into the directory specified.

In the formsweb.cfg create a config section something like: [my_frd] otherparams=record=collect log=my_frd.txt form=my_form.fmx

Then call this from a url using the config section.
Example: http://my_machine:my_port/forms/frmservlet?config=my_frd

How to create a FRD (Forms Runtime Diagnostic) Log in EBusiness Suite R12 using Forms 10g

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"http://testserver.oracle.com:8005/forms/frmservlet"to be the value for the USER.

2. Append the USER value of ICX: Forms Launcher with the "?record=collect" (without the quotes)
e.g. update the value of ICX: Forms Launcher for the user to behttp://testserver.oracle.com:8005/forms/frmservlet?record=collect
Another method is to set the "Forms Runtime Parameters" profile option with a value of "record=collect" (without quotes)

3. Save this change at the USER level.

4. Logout and Log back in again, for this profile to take effect. When you login again, a message box pops up, which alerts you that Diagnostics is enabled.

5. Go to Help->About Oracle Applications, go to the section
----------------------------------------
Forms Server Environment Variables
----------------------------------------
There you should see a FORMS_TRACE_DIR. Note the value of this variable.

If you find that the FORMS_TRACE_DIR is not defined, then ask your system administrator to:
- bring down the Forms server- define the "s_forms_trace_dir" context variable in the middle tier (Forms tier) to point to a valid directory. For this the preferred method is to use Oracle Applications Manager => Site Map link => System Configuration section => AutoConfig => for the Applications tier, click the Edit Parameters => System tab => click the + sign to expand the "oa_forms_server". In this expanded area, look for Title = "Forms runtime file directory location" (OA_VAR = "s_forms_trace_dir"). On this line, you can see the text box where the current value exists (if any).Enter/modify the value as desired here, and save.- run Autoconfig- then bring back up the Forms sever.

6. Reproduce the Forms-Issue, which you are trying to diagnose.

7. Go to the directory specified in the FORMS_TRACE_DIR variable. List the latest files. The FRD Log should be the one with the string "collect" in its name.

How to create a FRD (Forms Runtime Diagnostic) Log in EBusiness Suite R12 using Forms 10g

To create a FRD (Forms Runtime Diagnostic) Log in EBusiness Suite R12 using Forms 10g, perform the following steps:
1. Make the USER value for profile option 'ICX: Forms Launcher' the same as the SITE value
2. Append the USER value of ICX: Forms Launcher with the "?record=collect" (without the quotes)
e.g. update the value of ICX: Forms Launcher for the user to be"http://testserver.oracle.com:8005/forms/frmservlet?record=collect"
3. Save this change at the USER level.
4. Logout and Log back in again, for this profile to take effect. When you login again, a message box pops up, which alerts you that Diagnostics is enabled.
5. Go to Help->About Oracle Applications, go to the section

----------------------------------------
Forms Server Environment Variables
----------------------------------------

note the value of FORMS_TRACE_DIR. If it is empty,This value can be defined by the following steps:

- Bring down the Forms server
- Open the context ile and define the "s_forms_trace_dir" context variable in the middle tier (Forms tier) to point to a valid directory.
- Run Autoconfig- bring back up the Forms sever.

6. Reproduce the Forms-Issue, which you are trying to diagnose.
7. Go to the directory specified in the FORMS_TRACE_DIR variable. List the latest files. The FRD Log is the one with the string "collect" in its name.

Creating FRD (Forms Runtime Diagnostic) log in Oracle Applications R12

Forms Runtime Diagnostic (FRD) is a runtime event-based logging system intended to aid in the debugging of Forms applications. FRD is enabled at runtime on a user by user basis. When a form is run with FRD enabled, a combination of external user-application interactions and internal Forms processing events are written in chronological order to a log on the file system.

The following steps shows how to create a FRD (Forms Runtime Diagnostic) Log in EBusiness Suite R12 using Forms 10g

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

"http://testserver.oracle.com:8005/forms/frmservlet"

to be the value for the USER.

2. Append the USER value of ICX: Forms Launcher with the "?record=collect" (without the quotes)

e.g. update the value of ICX: Forms Launcher for the user to be

"http://testserver.oracle.com:8005/forms/frmservlet?record=collect"

3. Save this change at the USER level.

4. Logout and Log back in again, for this profile to take effect. When you login again, a message box pops up, which alerts you that Diagnostics is enabled.

5. Go to Help->About Oracle Applications, go to the section

----------------------------------------

Forms Server Environment Variables

----------------------------------------

There you should see a FORMS_TRACE_DIR. Note the value of this variable.

P.S: If you find that the FORMS_TRACE_DIR is not defined, then ask your sysadmin to bring down the forms server, define this environment variable in the middle tier (form tier) to point to a valid directory, and then bring the forms-sever back up .

6. Reproduce the Forms-Issue, which you are trying to diagnose.

7. Go to the directory specified in the FORMS_TRACE_DIR variable. List the latest files. The FRD Log should be the one with the string "collect" in its name.