Managing Oracle Fusion Applications Log Files

如何使用Oracle Fusion Applications日志文件？

Oracle Fusion Applications很大很多，后面的运维和对customer success的支持离不开后台log file。如果找到正确的log文件和如何设置log level都是挑战。官方给出这个文档以帮助Oracle Fusion Applications的系统运维和开发支持。

https://docs.oracle.com/cd/E36909_01/fusionapps.1111/e14496/log-files.htm

大体有下面几个章节，可以整理下。

• Section 15.1, "Overview of Oracle Fusion Applications Incidents, Logging, and QuickTrace"

• Section 15.2, "Understanding Oracle Fusion Applications Log Files and Log Messages"

• Section 15.3, "Viewing and Searching Log Files During Normal Operation"

• Section 15.4, "Configuring Settings for Log Files During Normal Operation"

本文的一些关键词以供快速参考。

Incidents, log files, QuickTrace, Cloud Control, Support Workbench

Information Technology Infrastructure Library (ITIL)

Oracle Diagnostic Logging (ODL), message structure

logging level, profile options

AFLOG_SettingName , AFLOG_ENABLED, AFLOG_LEVEL, AFLOG_MODULE,  FND_MESSAGE_MODE 

 

（一）Oracle Fusion Applications Incidents, logging, and QuickTrace 概览和简介

Incidents, log files, and QuickTrace can all help you administer Oracle Fusion Applications. If your Oracle Fusion Applications environment includes Oracle Enterprise Manager Cloud Control (Cloud Control), then you can also use Support Workbench to help you investigate, report, and resolve problems.

Incidents are collections of information about error conditions. It is strongly recommended that you follow Information Technology Infrastructure Library (ITIL) best practices by establishing a help desk or service desk within your organization to support Oracle Fusion Applications, and have the help desk personnel use incidents to track the troubleshooting and resolution of all problems. Some incidents are created and gather information automatically when problems occur. For example, the information associated with an automatically created incident may include detailed operational information collected by the QuickTrace (in-memory logging) feature for Oracle Fusion Applications. For problems that do not automatically create incidents, administrators or help desk personnel can manually create incidents and manually gather and add related system information.

Log files contain information about both normal and problematic events. Log files can help you both to monitor normal operations and to diagnose and address some problems yourself. For example, log messages that state that a service cannot be reached might indicate a hardware failure. If you discover a more complex issue, then Oracle Support personnel may use log files to trace the execution code paths of relevant requests, as part of diagnosing the problem. Log files are particularly helpful if your Oracle implementation contains custom code that needs debugging, especially when using a debugger is not feasible, such as on a production system.

The QuickTrace (in-memory logging) feature continuously records a specified level of log detail in an area of memory. The memory is recycled on an ongoing basis, with the oldest information being deleted or overwritten first. Because QuickTrace writes to memory instead of to a log file, it can gather operational information continuously without significantly affecting system performance. The information that QuickTrace stores in memory is written to disk only when an incident occurs or when an administrator manually dumps the contents of a QuickTrace buffer.

In Cloud Control, Support Workbench helps you investigate, report, and resolve problems (critical errors). You can use Support Workbench to perform the following kinds of operations:

1）View summary information about recent problems and incidents.
2）View detailed diagnostic data that was gathered automatically.
3）Manually trigger additional dumps of diagnostic data.
4）Connect to the Oracle Fusion Applications Diagnostic Dashboard application (Diagnostic Dashboard), which provides you with additional diagnostic tests that you can run. For information about using Diagnostic Dashboard, see Chapter 16 and the "Troubleshooting Oracle Fusion Applications Using Incidents, Logs, QuickTrace, and Diagnostic Tests" chapter in the Oracle Fusion Applications Administrator's Troubleshooting Guide.
5）Create or update service requests with Oracle Support, including uploading diagnostic data to Oracle

For information about using Support Workbench to administer Oracle Fusion Applications targets, specifically, see the "Troubleshooting Oracle Fusion Applications Using Incidents, Logs, QuickTrace, and Diagnostic Tests" chapter in the Oracle Fusion Applications Administrator's Troubleshooting Guide. For general information about using Support Workbench, see the topic "Support Workbench Page" in the Cloud Control online help and the chapter on investigating, reporting, and resolving problems in Oracle Database 2 Day DBA.

 

(二)理解Oracle Fusion Application(FA) Log Files and Log messages

• Section 15.2.1, "Standard Log File Administration Tasks and Tools"

• Section 15.2.2, "Log Files and Settings"

• Section 15.2.3, "Log Message Structure"

有两个概念必须先理解下，对我们看log有帮助。

• Seed data is information that Oracle provides to you in the form of database records. Error messages are included in seed data.

• Profiles are settings that you can select to determine details of how the application operates. Oracle Fusion applications include profile options that affect how much information to log either for an entire site or for a specific user. Oracle Fusion applications that are written in Java also support some profile options that affect how much information to log for a specific product.

In particular, you can use Fusion Applications Control to configure log profile option values for Oracle Fusion Applications, although you can also configure profile options by using the Manage Administrator Profile Values screen in the Setup and Maintenance work area.

 

A typical log message consists of three parts （message structure）:

• Attributes that are logged by the Oracle Fusion Middleware layer or the Oracle Database layer

• Attributes that are logged by logging APIs for Oracle Fusion Applications, including AppsLogger

• Message text

This section contains the following topics:

• Section 15.2.3.1, "Log Message Attributes Supplied by the Oracle Fusion Middleware and Oracle Database Layers"

• Section 15.2.3.2, "Log Message Attributes Supplied by Logging APIs for Oracle Fusion Applications"

• Section 15.2.3.3, "Log Message Attributes Supplied by the Application Session"

• Section 15.2.3.4, "Log Message Attributes Supplied by Oracle Enterprise Scheduler Job Requests"

• Section 15.2.3.5, "Log Message Attributes Supplied by SOA"

 

 

(三）如何有效的查看和搜索日志文件

 To view and search Oracle Fusion application log files effectively, it is important to be familiar with the software that is available for working with log files. You may also find it helpful to know where log files are stored for various application modules.

This section contains the following topics:

 

• Section 15.3.1, "Viewing Logs from Fusion Applications Control"

• Section 15.3.2, "Searching for Specific Information in Log Files within a Single Domain"

• Section 15.3.3, "Searching for Specific Information in Log Files Across Multiple Domains"

• Section 15.3.4, "Saving Log Search Criteria for Reuse"

• Section 15.3.5, "Reusing Saved Log Search Criteria"

• Section 15.3.6, "Typical Log File Locations"

• Section 15.3.7, "Location of Logged Information When Using Multiple Managed Servers"

 

(四)如何设置日志的配置

Although critical business logic sections of Oracle Fusion applications may write more information to log files than less critical areas of the application code, the amount of information that Oracle Fusion applications log depends primarily on how the environment is configured. Oracle supplies default values for log settings, but you can specify different setting values if you want to adjust the amount of information to be logged. Most Oracle Fusion Applications components use a standard set of log configuration settings. For information about the selected components that use nonstandard log settings, see Section 15.4.6.

This section contains the following topics:

• Section 15.4.1, "Default System Log Settings"

• Section 15.4.2, "When Changes to Log File Configuration Settings Take Effect"

• Section 15.4.3, "Standard Logging Levels"

• Section 15.4.4, "Managing Log File Size and Disk Space Usage"

• Section 15.4.5, "Using Profile Options to Configure Standard Log Settings"

• Section 15.4.6, "Using Additional Settings to Configure Logs for Selected Components"

• Section 15.4.7, "Configuring Access to Logs for Fusion Applications Control"

To set logging levels either for a whole site or for a particular user, administrators change profile option values from either the Log Configuration dialog in Fusion Applications Control or the Manage Administrator Profile Values screen in the Setup and Maintenance work area. 

To set logging levels for a particular product (for Oracle Fusion applications written in Java, only), administrators change profile option values from the Manage Administrator Profile Value screen in the Setup and Maintenance work area.

Under certain specific conditions, Oracle Fusion Applications users can set their own profile option for logging levels, from the Troubleshooting Options dialog under the Oracle Fusion Applications Help > Troubleshooting menu. Setting a logging level for a particular user is useful if you want only that user to gather more detailed log information while attempting to reproduce a problem. However, the Help > Troubleshooting menu displays the Troubleshooting Options command only for Oracle Fusion Applications users who have a job role that is mapped to the following three duty roles:

• Supportability Level Management Duty (CRM) (FND_SET_SUPPORTABILITY_LEVEL_DUTY_CRM)

• Supportability Level Management Duty (FSCM) (FND_SUPPORTABILITY_LEVEL_MANAGEMENT_DUTY_FSCM)

• Supportability Level Management Duty (HCM) (FND_SUPPORTABILITY_LEVEL_MANAGEMENT_DUTY_HCM)