Viewing the Performance of Oracle Fusion Middleware

12 Managing Log Files and Diagnostic Data 12-1 12 Managing Log Files and Diagnostic Data Oracle Fusion Middleware components generate log files containing messages that record all types of events, including startup and shutdown information, errors, warning messages, and access information on HTTP requests. This chapter describes how to find information about the cause of an error and its corrective action and to view and manage log files to assist in monitoring system activity and in diagnosing problems. It contains the following topics: ■ Overview of Oracle Fusion Middleware Logging ■ Understanding ODL Messages and ODL Log Files ■ Viewing and Searching Log Files ■ Configuring Settings for Log Files ■ Correlating Messages Across Log Files and Components ■ Configuring Tracing

12.1 Overview of Oracle Fusion Middleware Logging

Most Oracle Fusion Middleware components write diagnostic log files in the Oracle Diagnostic Logging ODL format. Log file naming and the format of the contents of log files conforms to an Oracle standard. By default, the diagnostic messages are written in text format. ODL provides the following benefits: ■ The capability to limit the total amount of diagnostic information saved. ■ Older segment files are removed and newer segment files are saved in chronological fashion. ■ Components can remain active, and do not need to be shutdown, when older diagnostic logging files are deleted. You can view log files using Fusion Middleware Control or the WLST displayLogs command, or you can download log files to your local client and view them using another tool for example, a text editor or another file viewing utility. Note: For information about logging for IBM WebSphere, see Configuring Oracle Fusion Middleware Logging on IBM WebSphere in the Oracle Fusion Middleware Third-Party Application Server Guide. 12-2 Oracle Fusion Middleware Administrators Guide

12.2 Understanding ODL Messages and ODL Log Files

Using ODL, diagnostic messages are written to log files and each message includes information, such as the time, component ID, and user. The following example shows an ODL format error messages from Oracle SOA Suite: [2010-09-23T10:54:00.206-07:00] [soa_server1] [NOTIFICATION] [] [oracle.mds] [tid: [STANDBY].ExecuteThread: 1 for queue: weblogic.kernel.Default self-tuning] [userId: anonymous] [ecid: 0000I3K7DCnAhKB5JZ4Eyf19wAgN000001,0] [APP: wsm-pm] Metadata Services: Metadata archive MAR not found. In the message, the fields map to the following attributes, which are described in Table 12–1 : ■ Timestamp, originating: 2010-09-23T10:54:00.206-07:00 ■ Organization ID: soa_server1 ■ Message Type: NOTIFICATION ■ Component ID: oracle.mds ■ Thread ID: tid: [STANDBY].ExecuteThread: 1 for queue: weblogic.kernel.Default self-tuning ■ User ID: userId: anonymous ■ Execution Context ID: ecid: 0000I3K7DCnAhKB5JZ4Eyf19wAgN000001,0 ■ Supplemental Attribute: APP: wsm-pm ■ Message Text: Metadata Services: Metadata archive MAR not found. By default, the information is written to the log files in ODL text format. You can change the format to ODL XML format, as described in Section 12.4.4 . Table 12–1 describes the contents of an ODL message. For any given component, the optional attributes may not be present in the generated diagnostic messages. Note: Oracle WebLogic Server does not use the ODL format. For information about the Oracle WebLogic Server log format, see Oracle Fusion Middleware Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server. Table 12–1 ODL Format Message Fields Attribute Name Description Required Timestamp, Originating TIME The date and time when the message was generated. This reflects the local time zone. Yes Timestamp, normalized time_norm The timestamp normalized for clock drift across hosts. This field is used when the diagnostic message is copied to a repository on a different host. No Organization ID org_id The organization ID for the originating component. The ID is oracle for all Oracle components. No INSTANCE_ID INST_ID The name of the Oracle instance to which the component that originated the message belongs. No COMPONENT ID COMP The ID of the component that originated the message. Yes