Wednesday, June 27, 2012

Forms Trace / Diagnostics Oracle Apps

Tracing in R12
  1. Set the user value for profile option 'ICX: Forms Launcher' to be 'http://hostname.domain:port/forms/frmservlet?record=collect+log=user1.log'. Use without quotes and you can replace "user1" with your own.
  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 or "echo $FORMS_TRACE_DIR" to get existing value. Note: by default, this directory is named forms_.trc, where is the process identifier.
Tracing in 11.5.10
  1. Make the user value for profile option 'ICX: Forms Launcher' the same as the site value.
    e.g. 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. For example,update the value of ICX: Forms Launcher for the user to be: 'http://testserver.oracle.com:8005/dev60cgi/f60cgi?record=all&log=username_frd.log'
  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.

No comments:

Post a Comment