In the Display Event Log Entries for Request field, select Yes to display Click Submit.

9 Logging 9-1 9 Logging The logging feature of Oracle Web Cache enables you to troubleshoot difficulties you might have in execution and use of Oracle Web Cache and associated processes. This chapter includes the following topics: ■ Section 9.1, Introduction to Event Logs ■ Section 9.2, Introduction to Access Logs ■ Section 9.3, Configuring Event Logs ■ Section 9.4, Configuring Access Logs ■ Section 9.5, Creating a Customized Access Log Format ■ Section 9.6, Creating a Customized Access Log Rollover Policy ■ Section 9.7, Viewing Event Logs and Access Logs ■ Section 9.8, Rolling Over Event and Access Logs ■ Section 9.9, Using Audit Logs

9.1 Introduction to Event Logs

Oracle Web Cache records event and error information in event logs. An event log entry can help you determine what objects have been inserted in the cache and alert you to any cache-related issues. By default, Oracle Web Cache collects all event log messages associated with each request in memory. If the most severe message in the request is at or above the selected verbosity level, Oracle Web Cache writes all the messages related to the request to the event log at once. Oracle Web Cache groups the messages for the request together in the log file for easier diagnosis. By default, the event log has a file name of event_log for the Oracle Web Cache and Oracle Diagnostic Logging ODL text formats and log.xml for the ODL XML format. Oracle Web Cache stores logs files in the following directories: UNIX ORACLE_INSTANCEdiagnosticslogsWebCachewebcache_name Windows ORACLE_INSTANCE\diagnostics\logs\WebCache\webcache_name This section includes the following topics: ■ Section 9.1.1, Event Logging Formats ■ Section 9.1.2, Event Log Examples

9.1.1 Event Logging Formats

When you configure settings for event logs, select the logging format: 9-2 Oracle Fusion Middleware Administrators Guide for Oracle Web Cache ■ Section 9.1.1.1, Oracle Diagnostics Logging Text and XML Formats ■ Section 9.1.1.2, Oracle Web Cache Classic Format

9.1.1.1 Oracle Diagnostics Logging Text and XML Formats

The Oracle Diagnostic Logging ODL format provides a common format for all diagnostic messages and log files, and a mechanism for correlating the diagnostic messages from various components across Oracle Fusion Middleware. You can select ODL Text to create a text file or ODL XML to create an XML file. The format of the ODL Text format follows: [TSTZ_ORIGINATING] [MSG_TYPE:MSG_ID] [MODULE_ID;MSG_LEVEL] [MODULE_ID] [ECID] MSG_ TEXT Table 9–4 describes the fields for the ODL Text format. The following shows an event log excerpt with the ODL Text format: [2008-11-04T05:55:35-05:00] [webcache] [NOTIFICATION:1] [WXE-08513] [logging] [ecid: ] Cache server process ID 11679 is starting up. [2008-11-04T05:55:35-05:00] [webcache] [NOTIFICATION:1] [WXE-09612] [main] [ecid: ] Oracle Web Cache 11g 11.1.1 [2008-11-04T05:55:35-05:00] [webcache] [NOTIFICATION:1] [WXE-13002] [config] [ecid: ] Maximum allowed incoming connections are 700 [2008-11-04T05:55:35-05:00] [webcache] [NOTIFICATION:1] [WXE-09446] [stats] [ecid: ] Statistics initialization commencing. [2008-11-04T05:55:35-05:00] [webcache] [NOTIFICATION:1] [WXE-09441] [stats] [ecid: ] DMS enabled Table 9–1 ODL Text Message Fields Fields Description TSTZ_ORIGINATING The date and time when the message was generated. Time is either displayed in local or Greenwich Mean Time. MSG_TYPE The type of message. Possible values are NOTIFICATION, WARNING, TRACE, and DEBUG. 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. 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: WXE-08513. The Oracle Fusion Middleware Error Messages Reference describes the messages in further detail. MODULE_ID The ID of the module that originated the message. If the component is a single module, the component ID is listed for this attribute. 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 Also: Section 9.1.1.4 for more information about the Oracle-ECID request header MSG_TEXT The text of the error message. Logging 9-3 [2008-11-04T05:55:35-05:00] [webcache] [NOTIFICATION:1] [WXE-09447] [stats] [ecid: ] Statistics initialization complete. [2008-11-04T05:55:36-05:00] [webcache] [NOTIFICATION:1] [WXE-12209] [cluster] [ecid: ] A 1 node cluster successfully initialized [2008-11-04T05:55:36-05:00] [webcache] [NOTIFICATION:1] [WXE-09614] [main] [ecid: ] The following Oracle Web Cache internal files are pre-populated to the cache: [[host:port_oracle_http_server_webcache_static_.html]] Table 9–2 describes the fields for the ODL XML format. The ODL XML Format provides additional fields, such as the following shows an event log excerpt for the ODL XML format: MESSAGE HEADER TSTZ_ORIGINATING2008-11-04T06:07:14.0116-05:00TSTZ_ORIGINATING COMPONENT_IDWXECOMPONENT_ID MSG_ID8513MSG_ID MSG_TYPE TYPE=NOTIFICATIONMSG_TYPE MSG_LEVEL1MSG_LEVEL HOST_IDhostHOST_ID HOST_NWADDR10.10.150.35HOST_NWADDR MODULE_IDloggingMODULE_ID HEADER CORRELATION_DATA EXEC_CONTEXT_ID Table 9–2 ODL XML Message Fields Fields Description TSTZ_ORIGINATING The date and time when the message was generated. Time is either displayed in local or Greenwich Mean Time. COMPONENT_ID The ID of the component that originated the message. 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: WXE-08513. MSG_TYPE The type of message. Possible values are NOTIFICATION, WARNING, TRACE, and DEBUG. 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. HOST_ID The name of the host where the message originated. HOST_NWADDR The network address of the host where the message originated. MODULE_ID The ID of the module that originated the message. If the component is a single module, the component ID is listed for this attribute. 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 Also: Section 9.1.1.4 for more information about the Oracle-ECID request header MSG_TEXT The text of the error message.