Skip Headers
Oracle® Fusion Middleware Release Notes
11g Release 1 (11.1.1) for Linux x86-64

Part Number E14770-31
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

44 Log Files and Diagnostic Testing

This chapter describes issues associated with Oracle Fusion Applications log files and diagnostic testing. It includes the following topics:

44.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

44.1.1 Product Level Not Supported for Logging Profile Options

Logging profile options for the Product level are enabled, but the Product level is not supported for logging profile options at this time.

44.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

44.2.1 Requirements for Scheduling Diagnostic Tests

The ability to schedule diagnostic tests is supported only if the Oracle Fusion Applications configuration that you provisioned includes Oracle Enterprise Scheduler.

44.2.2 Enabling the diagctl.sh Command Line Interface for Diagnostic Testing

In the current release, you must complete certain manual configuration steps in order to perform diagnostic tests using the diagctl.sh command line interface.

To make the diagctl.sh command line interface available for diagnostic testing:

  1. Use an account that has administrative privileges to log in to the operating system of an Oracle Fusion Applications domain's primordial host.

  2. Navigate to the APPLICATIONS_BASE/domains/primordial_host_name/CommonDomain/config/fmwconfig/ directory, replacing APPLICATIONS_BASE with the path to the root directory under which the provisioned environment resides and primordial_host_name with the name of the primordial host.

  3. Copy the jps-config-jse.xml file to the directory that contains the diagctl.sh file, APPLICATIONS_BASE/fusionapps/atgpf/bin.

  4. Navigate to APPLICATIONS_BASE/fusionapps/atgpf/bin.

  5. Using a text editor of your choice, add the following lines to your copy of the jps-config-jse.xml file, placing the new lines between <jpsContexts> and </jpsContexts>, and then save the file.

    <jpsContext name="appsdiag">
    <serviceInstanceRef ref="credstore.ldap"/>
    <serviceInstanceRef ref="policystore.ldap"/>
    <serviceInstanceRef ref="idstore.ldap"/>
    <serviceInstanceRef ref="idstore.loginmodule"/>
    </jpsContext>
    
  6. As a general precaution, it is recommended that you make a backup copy of the diagctl.sh file.

  7. While still in the APPLICATIONS_BASE/fusionapps/atgpf/bin directory, use a text editor to open the original diagctl.sh file and locate the following line in the file:

    APPLCORE_LIBDIR="${JBHOME}/jdev/oaext/adflib"

  8. Modify this line to read as follows and then save the file:

    APPLCORE_LIBDIR="${MW_HOME}/atgpf/atgpf/modules/oracle.applcore.model_11.1.1"

  9. For any administrative account that needs to use the diagctl.sh command line interface, use a command such as the following to set the DIAGJPSCONFILEFILE environment variable to the location of the modified jps-config-jse.xml file.

    setenv DIAGJPSCONFIGFILE APPLICATIONS_BASE/fusionapps/atgpf/bin/jps-config-jse.xml

NOTE: For successful authentication, the DIAGJPSCONFIGFILE environment variable must be correctly set for any operating system session in which the diagctl.sh command line interface is used.

After you complete these steps, you can run diagctl.sh from the primordial host.

44.2.3 Entering Database Version, OS Version, and JDK Version

The AFLOG_EXTENDED_ENABLED profile option determines whether to log the following extended attributes: Message Cause, User Action, User Details, Admin Action, and Admin Details. When the value of this profile option is N, none of these extended profile options is logged.In the current release, when the value of the AFLOG_EXTENDED_ENABLED profile option is Y, the Message Cause extended attribute is always logged. The additional extended attributes that are logged depend on the value of the FND_MESSAGE_MODE profile option.When the value of the AFLOG_EXTENDED_ENABLED profile option is Y and the value of the FND_MESSAGE_MODE profile option is USER, the User Action and User Details extended attributes are logged, along with Message Cause.When the value of the AFLOG_EXTENDED_ENABLED profile option is Y and the value of the FND_MESSAGE_MODE profile option is ADMIN, the Admin Action and Admin Details extended attributes are logged, along with Message Cause.

44.3 Documentation Errata

There are no documentation errata items at this time.