FRD trace

Note 167635.1

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.

With the Latest Patch Levels or 11.5.10 you are no longer allowed to enter directly into the Applications Forms via the /dev60cgi/f60cgi URL. it is UNSUPPORTED to log directly to the Forms via /dev60cgi/f60cgi, but we do allow it for FRD Traces only.
Suggestion: Create a user "TRACE" and set above profile for it. When a FRD is needed ask user to use this username.

2. Append the user value of ICX: Forms Launcher with the Forms parameters for FRD. For example, 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

http://testserver.us.oracle.com:9004/dev60cgi/f60cgi?play=&record=
collect&log=form1.frd

This log file will show each keystroke so it will build very fast, A good practice is on intermittent errors that the log file be periodically deleted, so that the file does not become so massive that it hinders investigation of the cause of the error.

3. Login to the Personal Home Page, navigate to the form and perform the steps that you wish to trace for the user the profile above was set for.

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. $FORMS60_TRACE_PATH was introduced with Forms Patchset 16..

Set your $FORMS60_TRACE_PATH variable to a Location from where you would like your frd trace files to be copied to or leave as the default.

This was changed for Security reason, so that the Sysadmin's can maintain Security on the Servers.
---------

Then please upload your output to this SR, then will deliver to development part for further analyzing.