How To Generate A Stack Trace For Forms With Applications 11i

Print this post

 

When troubleshooting forms issues such as FRM-92100, it is often useful to generate a stack trace. Below are the steps for Applications DBAs to follow to produce a stack trace for forms in an Oracle EBusiness Suite 11i environment. Solution 1. Set the following environment variables:     a) check the value of $FORMS60_TRACE_PATH and make sure this directory has write permissions and     has space.     b) set $FORMS60_CATCHTERM=0     2. If your platform is Unix, check that the operating system ulimit values are sufficient.     Run `ulimit -a` as the applmgr, assuming applmgr starts the forms server,     to check the memory, data and stack sizes.     3. Stop the forms server. 4. Backup file f60webmx and then relink this executable with debug symbols.     Make sure you are signed in as the user who owns f60webmx executable, then run this command:     adrelink.sh force=y ranlib=y link_debug=y "fnd f60webmx"     5. Start the forms server.     6. Reproduce the forms error that you are investigating. 7. Check for a new core file in the following directories: a) $FORMS60_TRACE_PATH directory.  or b) check the $PWD directory for the forms server.    By default in an Autoconfig enabled environment, this is the directory in which the adfrmctl.sh starts;    $PWD is $COMMON_TOP/admin/scripts/<context>/ directory.     To confirm the $PWD directory setting, you can also check by opening any form and navigating to          Help->Diagnostics->Examine             In field 1 select $environment$             In field 2 enter PWD (no $ or quotes)            The value is populated automatically when you select the tab key.