Configuring Apache HTTP Server for Static File Caching Configuring Oracle HTTP Server for Static File Caching

7-38 System Administrators Guide for Oracle Business Intelligence Enterprise Edition Part IV Part IV Resolving Issues This part explains how to resolve issues in Oracle Business Intelligence. It includes the following chapters: ■ Chapter 8, Diagnosing and Resolving Issues in Oracle Business Intelligence ■ Chapter 9, Managing Usage Tracking 8 1 Diagnosing and Resolving Issues in Oracle Business Intelligence 8-1 8 Diagnosing and Resolving Issues in Oracle Business Intelligence This chapter describes how to diagnose and resolve issues and includes the following topics: ■ Section 8.1, How Are Issues Resolved? ■ Section 8.2, Viewing And Configuring Diagnostic Log Files ■ Section 8.3, Understanding Diagnostic Log and Log Configuration Files ■ Section 8.4, Managing the Query Log ■ Section 8.5, Logging in Oracle BI Presentation Services 8.1 How Are Issues Resolved? Oracle Business Intelligence provides easy ways to find the causes and solutions to issues. You can do the following to resolve issues: ■ View recent issues with the system on the Overview page in Fusion Middleware Control. ■ Drill into the problems using the diagnostics pages in Fusion Middleware Control. ■ Track issues across components for example, regarding performance or availability. ■ View the log files from within Fusion Middleware Control. ■ Resolve the issues by changing configuration of the Oracle Business Intelligence system. The principal activities that you perform to support issue resolution include: ■ Examination and configuration of error and diagnostic log information. For information, see: – Section 8.2, Viewing And Configuring Diagnostic Log Files – Section 8.3, Understanding Diagnostic Log and Log Configuration Files – Section 8.4, Managing the Query Log – Section 8.5, Logging in Oracle BI Presentation Services ■ Examination of system and process metrics to understand availability and performance issues. For information, see: – Chapter 7, Managing Performance Tuning and Query Caching 8-2 System Administrators Guide for Oracle Business Intelligence Enterprise Edition

8.2 Viewing And Configuring Diagnostic Log Files

You can view diagnostic log files and configure settings that affect diagnostic log files and the information that they contain, as described in the following sections: ■ Section 8.2.1, Using Fusion Middleware Control to View Log Information, Error Messages, and Alerts ■ Section 8.2.2, Configuring Log File Rotation Policy and Specifying Log Levels

8.2.1 Using Fusion Middleware Control to View Log Information, Error Messages, and Alerts

You can search for and view the log entries for Oracle Business Intelligence components using Fusion Middleware Control Log Viewer. The log files can be searched for log messages, and you can apply filters that can, for example, target a certain date range, user, user transaction, or level of message error, warning, notification, and so on. You can also view log files in their entirety from the Fusion Middleware Control Log Viewer. When log entries for error messages and warnings are generated across multiple log files, they can be difficult to trace. However, it is possible to view logging information for specific user transactions across multiple log files. Transaction level logging associates a unique transaction ID, which is called the Execution Context ID ECID, with every log and error message that is generated in response to a user request. This logging enables rapid diagnosis of the cause of underlying issues. However, some messages in the log for example system messages for server startup or shutdown do not have a transactional attribute. All log messages that are related to client requests do have a transactional attribute. Before you begin this procedure, ensure that you are familiar with the information in Section 3.2, Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings. To use Fusion Middleware Control to view log information, error messages, and alerts: 1. Go to the Business Intelligence Overview page, as described in Section 2.2.2, Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components. 2. Display the Diagnostics page. Click the Help button on the page to access the page-level help for its elements. 3. View lists of the following: ■ recent errors under the Most Recent Errors region ■ recent warnings under the Most Recent Warnings region 4. Select a link under ViewSearch All Log Files and ViewSearch Log Files By Component to display messages for all log files, or for the messages for the log files of a specified component. Click the Help button on the page to access the page-level help for the following links: ■ Search the log files using the Log Viewer ■ Presentation Services Log ■ Server Log ■ Scheduler Log Diagnosing and Resolving Issues in Oracle Business Intelligence 8-3 ■ JavaHost Log ■ Cluster Controller Log ■ Action Services Log ■ Security Services Log ■ Administrator Services Log Fusion Middleware Control displays messages in the Log Messages page that correspond to your selection. 5. Enter appropriate search criteria to display corresponding error messages. To view messages by ECID, click View Related Messages and select the by ECID Execution Context ID menu option. 6. Select one or more rows to view the log file entry details for the selected messages. For more information about the elements that are displayed in the Log Viewer, see the Fusion Middleware help.

8.2.2 Configuring Log File Rotation Policy and Specifying Log Levels

You can configure criteria that determine when a new log file must be created, based on the size of the log file and the age of the log file. You can also specify log levels to determine what level of message the log files contain. This section contains the following topics: ■ Section 8.2.2.1, Using Fusion Middleware Control to Configure Log File Rotation Policy and Specify Log Levels ■ Section 8.2.2.2, Manually Changing Additional Log File Settings For information about using methods in the Oracle BI Systems Management API to change configuration settings, see Chapter 22, Introducing the Oracle BI Systems Management API.

8.2.2.1 Using Fusion Middleware Control to Configure Log File Rotation Policy and Specify Log Levels

Before you begin this procedure, ensure that you are familiar with the information in Section 3.2, Using Fusion Middleware Control to Update Oracle Business Intelligence Configuration Settings. To use Fusion Middleware Control to configure log file rotation policy and specify log levels: 1. Go to the Business Intelligence Overview page, as described in Section 2.2.2, Using Fusion Middleware Control to Manage Oracle Business Intelligence System Components. 2. Display the Diagnostics page.

3. Click Lock and Edit Configuration to enable changes to be made.

4. Complete the elements using the descriptions in the Help topic for the page. For example, you can specify which log levels to use, and for some you can set their granularity. Click the Help button on the page to access the page-level help for the following options: 8-4 System Administrators Guide for Oracle Business Intelligence Enterprise Edition Log Configuration ■ Maximum File Size option ■ Maximum Log Age option Query Logs ■ Maximum File Size option ■ Maximum Log Age option Log Levels ■ Incident Error option ■ Error option ■ Warning option ■ Notification option ■ Trace option

5. Click Apply, then click Activate Changes.

6. Return to the Business Intelligence Overview page and click Restart.

8.2.2.2 Manually Changing Additional Log File Settings

In addition to the log file settings that you can change in Fusion Middleware Control, you can change other settings manually. Use various elements in the log configuration file for a component to change these settings. Before you begin this procedure, ensure that you are familiar with the information in Section 3.4, Using a Text Editor to Update Configuration Settings. To manually change the settings that configure the log file format: 1. Open the component log configuration file as described in Section 8.3.2, What Are Diagnostic Log Configuration Files and Where Are They Located?

2. Locate the section in which you must add the Format element, which specifies the

log file format. The default is ODL-TEXT. To use the Fusion Middleware Control Log Viewer to view and search through the log files for Oracle Business Intelligence, then the files must be in either ODL-Text or ODL-XML format.

3. Include the element and its ancestor elements as appropriate, as shown in the

following example: server ServerInstance Log FormatODL-TEXTFormat Log ServerInstance server Note: Editing a diagnostic log configuration file for a single component is not advised, because changes might subsequently be overwritten. For information, see Section 3.4, Using a Text Editor to Update Configuration Settings. Diagnosing and Resolving Issues in Oracle Business Intelligence 8-5 For an example of a JavaHost Server diagnostic log configuration file, see Example 8–2 . 4. Save your changes and close the file. 5. Restart Oracle Business Intelligence.

8.3 Understanding Diagnostic Log and Log Configuration Files

This section discusses diagnostic log files and diagnostic log configuration files, and contains the following topics: ■ Section 8.3.1, What Are Diagnostic Log Files and Where Are They Located? ■ Section 8.3.2, What Are Diagnostic Log Configuration Files and Where Are They Located? ■ Section 8.3.3, What Are Log File Message Categories and Levels? ■ Section 8.3.4, What is Log File Rotation? 8.3.1 What Are Diagnostic Log Files and Where Are They Located? Diagnostic log files are files used to store message information that is generated by Oracle Business Intelligence servers. These log files are stored in the following location: ORACLE_INSTANCE\diagnostics\logs\component_type\coreapplication The following diagnostic log files are used in Oracle Business Intelligence: ■ Presentation Services – \CatalogCrawler\sawcatalogcrawlerlogsysn.log — The catalog crawler log file, which is not searchable in the Fusion Middleware Control Log Viewer. – sawlogn.log — The Presentation Services log file that represents the latest part of diagnostic log output and is searchable in the Fusion Middleware Control Log Viewer. For more information specifically about Presentation Services logging, see Section 8.5, Logging in Oracle BI Presentation Services. ■ Oracle BI Server – nqqueryn.log — The Oracle BI Server query log, which is not searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example nqquery-20101209-2135.log – nqservern.log — The Oracle BI Server main diagnostic log, which is searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example nqserver-20101209-2135.log – nqsadmintool.log — The log for the Oracle BI Administration Tool. – Oracle BI Server utilities — For example, biserverxmlexec and equalizerpds, also generate their own logs when they are run. ■ JavaHost – jh-n.log — The JavaHost Server main diagnostic log, which is searchable in the Fusion Middleware Control Log Viewer. n = date and timestamp, for example jh-20100909-2135.log