Viewing the Routing Topology

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 Managing Log Files and Diagnostic Data 12-3 For most Java components, the log file location is: UNIX MW_HOMEuser_projectsdomainsdomain_nameserversserver_namelogs Windows MW_HOME\user_projects\domains\domain_name\servers\server_name\logs The default name of a log file is server-name-diagnostic.log. For system components, the default log file location is: UNIX ORACLE_INSTANCEdiagnosticslogs Windows ORACLE_INSTANCE\diagnostics\logs Table 12–2 shows the log file location for components of Oracle Fusion Middleware. In the table, DOMAIN_HOME refers to the following directory, which is the WebLogic Server domain home: MW_HOMEuser_projectsdomainsdomain_name MESSAGE_ID MSG_ID The ID that uniquely identifies the message within the component. The ID consists of a prefix that represents the component, followed by a dash, then a 5-digit number. For example: OHS-51009 Yes MESSAGE_TYPE MSG_TYPE The type of message. Possible values are: INCIDENT_ERROR, ERROR, WARNING, NOTIFICATION, TRACE, and UNKNOWN. See Table 12–3 for information about the message types. Yes MESSAGE_LEVEL MSG_LEVEL The message level, represented by an integer value that qualifies the message type. Possible values are from 1 highest severity through 32 lowest severity. See Table 12–3 for information about the message levels. Yes HOST_ID HOST_ID The name of the host where the message originated. No HOST_NW_ADDR HOST_ADDR The network address of the host where the message originated. No MODULE_ID MODULE The ID of the module that originated the message. If the component is a single module, the component ID is listed for this attribute. Yes PROCESS_ID PID The process ID for the process or execution unit associated with the message. No THREAD_ID TID The ID of the thread that generated the message. No USER_ID USER The name of the user whose execution context generated the message. No ECID The Execution Context ID ECID, which is a global unique identifier of the execution of a particular request in which the originating component participates. You can use the ECID to correlate error messages from different components. See Section 12.5 for information about ECIDs. Yes RID The relationship ID RID, which distinguishes the work done in one thread on one process, from work done by any other threads on this and other processes, on behalf of the same request. See Section 12.5 for information about RIDs. No SUPPL_ATTRS An additional list of namevalue pairs which contain component-specific attributes about the event. No MESSAGE TEXT TEXT The text of the error message. Yes Message Arguments arg A list of arguments bound with the message text. No Supplemental Detail Supplemental information about the event, including more detailed information than the message text. No Table 12–1 Cont. ODL Format Message Fields Attribute Name Description Required 12-4 Oracle Fusion Middleware Administrators Guide In the table, ORACLE_INSTANCE refers to the following directory, which is the Oracle instance home: MW_HOMEinstance_name Table 12–2 Log File Location Component Log File Location Fusion Middleware Control DOMAIN_HOMEsysmanlogemoms.log DOMAIN_HOMEsysmanlogemoms.trc Oracle Application Development Framework DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Business Activity Monitoring DOMAIN_HOMEserversserver_namelogsbam-diagnostic.log Oracle Business Intelligence Discoverer DOMAIN_HOMEserversserver_ namelogsdiscovererserverdiagnostic.log DOMAIN_HOMEserversserver_namelogsdiscovererserver_ name-diagnostic.log DOMAIN_HOMEserversserver_namelogsdiscovererdiagnostic.log Oracle Business Process Management DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Directory Integration Platform DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Forms Services DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log ORACLE_ HOMEj2eeDevSuiteapplication-deploymentsformsapplication.log ORACLE_INSTANCEdiagnosticslogsFormsComponentforms ORACLE_INSTANCEdiagnosticslogsFRComponentdejvm Oracle Fusion Middleware Audit Framework DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle HTTP Server ORACLE_INSTANCEdiagnosticslogsOHScomponent_name.log Oracle Identity Federation DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Imaging and Process Management DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Information Rights Management DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Internet Directory ORACLE_INSTANCEdiagnosticslogsOIDcomponent_nameoid.log ORACLE_INSTANCEdiagnosticslogsOIDtools.log Oracle Platform Security Services DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Portal DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log ORACLE_INSTANCEdiagnosticslogsportal Oracle Reports ORACLE_INSTANCEdiagnosticslogsReportsServerComponentcomponent_ name ORACLE_INSTANCEdiagnosticslogsReportsBridgeComponentcomponent_ name ORACLE_INSTANCEdiagnosticslogsReportsToolsComponentcomponent_ name Oracle SOA Suite DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle TopLink DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle Virtual Directory ORACLE_INSTANCEdiagnosticslogsOVDcomponent_namediagnostic.log Managing Log Files and Diagnostic Data 12-5

12.3 Viewing and Searching Log Files

You can view, list, and search log files across Oracle Fusion Middleware components. You can view and search log files using Fusion Middleware Control or you can download a log file to your local client and view the log files using another tool. You can also list, view, and search log files using the WLST command-line tool. This section covers the following topics: ■ Viewing Log Files and Their Messages ■ Searching Log Files ■ Downloading Log Files Note the following about using the WLST commands to view the log files: ■ To use the custom WLST logging commands, you must invoke the WLST script from the Oracle Common home. See Section 3.5.1.1 for more information. ■ The log viewing commands work whether you are connected or not connected to a WebLogic server. If you are not connected, you must specify the path in the oracleInstance parameter. You specify either the WebLogic domain home, or the Oracle instance. ■ Most of the WLST logging commands require that you are running in the domainRuntime tree. For example, to connect and to run in the domainRuntime tree, use the following commands: .wlst.sh connectusername, password, localhost:port_number domainRuntime

12.3.1 Viewing Log Files and Their Messages

You can view the log files using Fusion Middleware Control or WLST commands, as described in the following topics: ■ Viewing Log Files and Their Messages Using Fusion Middleware Control ■ Viewing Log Files and Their Messages Using WLST Oracle Web Cache ORACLE_INSTANCEdiagnosticslogsWebCachecomponent_name.log Oracle Web Services Manager DOMAIN_HOMEserversserver_namelogsowsmmsglogging DOMAIN_HOMEserversserver_namelogsowsm-diagnostic.log Oracle WebCenter DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Oracle WebLogic Server DOMAIN_HOMEserversserver_namelogsserver-name-diagnostic.log Repository Creation Utility By default, writes to file specified in RCU_LOG_LOCATION. If not specified, attempts to write to the following locations: 1. ORACLE_HOMErculogtimestamp 2. tmplogdir.timestamp See Also: Logging Custom WLST Commands in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference Table 12–2 Cont. Log File Location Component Log File Location 12-6 Oracle Fusion Middleware Administrators Guide

12.3.1.1 Viewing Log Files and Their Messages Using Fusion Middleware Control

You can view the messages for all of the entities in a domain, an Oracle WebLogic Server, a component, or an application. For example, to view the log files and their messages for a Managed Server: 1. From the navigation pane, expand the farm, then WebLogic Domain, and then the domain. Right-click the Managed Server name and choose Logs, then View Log Messages. The Log Messages page is displayed. 2. Expand Selected Targets and in the row for a particular component or application, click the Target Log Files icon. The Log Files page is displayed. On this page, you can see a list of log files related to the Managed Server, as shown in the following figure: 3. Select a file and click View Log File. The View Log Files page is displayed. On this page, you can view the list of messages. 4. To view the details of a message, select the message. The details are displayed in the pane below the listing, as shown in the following figure: