Determine the OS version of a Linux Release/Kernel and Oracle Apps/DB

OS Commands:

[oracle@uswjusvr115 scripts]$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.6 (Santiago)

[oracle@uswjusvr115 scripts]$ cat /etc/oracle-release
Oracle Linux Server release 6.6

[oracle@uswjusvr115 scripts]$ cat /proc/version
Linux version 2.6.39-400.17.1.el6uek.x86_64 ( (gcc version 4.4.7 20120313              (Red Hat 4.4.7-3) (GCC) ) #1 SMP Fri Feb 22 18:16:18 PST 2013

*NOTE: uek = Unbreakable Enterprise Kernel 

[oracle@uswjusvr115 scripts]$ getconf LONG_BIT

[oracle@uswjusvr115 scripts]$ uname -a
            Linux 2.6.39-400.17.1.el6uek.x86_64 #1 SMP Fri Feb 22 18:16:18 PST 2013 x86_64               x86_64 x86_64 GNU/Linux

[oracle@uswjusvr115 scripts]$ uname -mrs
            Linux 2.6.39-400.17.1.el6uek.x86_64 x86_64

[oracle@uswjusvr115 scripts]$ cat /etc/issue
            Oracle Linux Server release 6.6
Kernel \r on an \m

SQL Command:

[oracle@uswjusvr115 scripts]$ sqlplus
           SQL*Plus: Release Production on Tue Oct 27 10:15:01 2015
SQL> select banner from v$version;
Oracle Database 11g Enterprise Edition Release – 64bit Production
PL/SQL Release – Production
CORE      Production
TNS for Linux: Version – Production
NLSRTL Version – Production

                       INSTANCE_NUMBER             INSTANCE_NAME HOST_NAME         VERSION
1              ebsprd

SQL> conn apps/apps
SQL> select release_name from apps.fnd_product_groups;

Enable Forms Diagnostics, Tracing in R12 using Profile Option

This document shows how to use Forms Runtime Diagnostics using Profile Option at user level.

  1. First verify if Forms using Socket or Servlet.
  • Login on to Application Server, and check the cfg file to verify the “serverURL=”And “connectMode=” settings.
  • In Servlet Mode:
  • In Socket Mode:


  1. Enable Forms Runtime Diagnostics (FRD)

FRD can be enabled in one of the following methods:

  • Option 1: Obtain FRD Trace Using Profile Options
  • Option 2: Obtain FRD Trace Using Appsweb.cfg
  • Option 3: Obtain FRD in an ADHOC way

We will be using method “Obtain FRD Trace Using Profile Options” in this example.

To start tracing, please modify Profile Option ‘ICX: Forms Launcher’ at USER level to include the Forms parameters required for FRD logging (Note: This should not set at SITE LEVEL)

2.1: Add the trace value “ ‘?record=collect’  “ to Apps URL for profile option ‘ICX: Forms Launcher’

In Servlet Mode:https://hostname.domain:port/forms/frmservlet?record=collect
in Socket Mode:https://hostname.domain:port/OA_HTML/frmservlet?record=collect


Copy the site level value for profile option ‘ICX: Forms Launcher’ and append values’?record=collect’. Past it at the user level.

Ex. Site Value:
Modified Value:

Copy the modified value to the User level and Save.


  1. Login into Oracle Applications and launch forms via self-service. Navigate through the steps to capture trace.

Should get below prompt when you login to Form.


  1. Obtain the Trace File. It’s in $FORMS_TRACE_DIR, where<pid> is the process identifier.

Ex: $FORMS_TRACE_DIR/collect_6540

<Sample Output file>


Source:R12: Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications (Doc ID 438652.1)