In the Session view, right-click the request in the Request window (bottom window) and click Kill Request

When you terminate a query request, the user who is initiating the query receives an error.

Session ID Unique internal identifier that the Oracle BI Server assigns each session when the session is initiated.

Start Time Time of the initial query request.

Status These are the possible values. Due to the speed at which some processes complete, not all values for any given request or session might appear.

■ Idle. There is presently no activity on the request or session. ■ Fetching. The request is being retrieved.

■ Fetched. The request has been retrieved.

■ Preparing. The request is being prepared for processing.

■ Prepared. The request has been prepared for processing and is ready

for execution.

■ Executing. The request is currently running. To terminate a request,

select it and click Kill Request. The user receives an informational message that indicates that the Oracle BI Administrator canceled the request.

■ Executed. The request has finished running.

■ Succeeded. The request ran to completion successfully. ■ Canceled. The request has been canceled.

■ Failed. An error was encountered during the processing or running

of the request.

Table 6–7 (Cont.) Request Window Columns (Bottom Window)

Troubleshooting an Oracle Business Intelligence Clustered Environment

Deploying Oracle Business Intelligence for High Availability 6-13

6.4.1.4 Server Information

Selecting Server info from the View menu provides information about the cluster server, such as server version number.

6.5 Troubleshooting an Oracle Business Intelligence Clustered

Environment

Use Fusion Middleware Control and the Administration Console to check the status of system processes. See Section 5.6.1, "Using Fusion Middleware Control to View System Component Availability" and Section 5.6.2, "Using the Administration Console to View Managed Server Availability" for more information.

After enabling clustering, load balancing, and failover capabilities, you can troubleshoot issues that might occur in the deployment using the following:

■ Messages and errors that are reported in Fusion Middleware Control

■ Log files for Oracle Business Intelligence components, also available through

Fusion Middleware Control

Review the log files for every Oracle Business Intelligence system component in the cluster. Log files record any client-side failures that might occur due to an incorrect configuration. Although some failover events are not logged, the Cluster Controller log file records crashes of any Oracle BI Scheduler or Oracle BI Server component. You can also review the Event Viewer log on Windows and the syslog on Linux or UNIX. See Chapter 8, "Diagnosing and Resolving Issues in Oracle Business Intelligence" for more information about log files.

6.5.1 Avoiding Errors with Network Appliance Devices When the Oracle BI Server Is

Running on Linux or UNIX

The following information applies to deployments with Oracle BI Server components on Linux or UNIX platforms that access Oracle Business Intelligence shared files and directories on a NAS device from Network Appliance. For environments with Oracle BI Server components on Linux or UNIX that use the NTFS security style, the

recommended Network Appliance Data ONTAP storage operating system version is 6.3.1 or later.

Linux or UNIX computers saving to an NTFS qtree in Data ONTAP versions 6.0.3 through 6.3 might see permission errors when trying to save designs. Use the

following Data ONTAP setting to silently ignore attempts to set UNIX permissions on NTFS qtrees after the design file is saved:

7

Managing Performance Tuning and Query Caching 7-1

7

Managing Performance Tuning and Query

Caching

This chapter provides information about ways to improve Oracle Business Intelligence query performance, including a performance tuning overview and information about monitoring system metrics. It also describes the how to manage and use the query cache, a feature that enables the Oracle BI Server to save the results of a query in cache files and then reuse those results later when a similar query is requested. Using cache, the cost of database processing must be paid only once for a query, not every time the query is run.

See also the following Oracle Fusion Middleware resources on performance tuning for your system:

Oracle Fusion Middleware Performance and Tuning Guide

Oracle Fusion Middleware Performance and Tuning for Oracle WebLogic Server

This chapter includes the following topics:

■ Section 7.1, "Monitoring Service Levels"

■ Section 7.2, "About Query Performance Tuning"

■ Section 7.3, "Setting Performance Parameters in Fusion Middleware Control" ■ Section 7.4, "About the Oracle BI Server Query Cache"

■ Section 7.5, "Configuring Query Caching"

■ Section 7.6, "Monitoring and Managing the Cache" ■ Section 7.7, "Strategies for Using the Cache"

■ Section 7.8, "Cache Event Processing with an Event Polling Table"

■ Section 7.9, "Managing the Oracle BI Presentation Services Cache Settings" ■ Section 7.10, "Improving Oracle BI Web Client Performance"

7.1 Monitoring Service Levels

Understanding service levels typically involves monitoring process state and viewing system metrics.

Oracle Business Intelligence automatically and continuously measures run-time performance in real time. The performance metrics are automatically enabled; you do not need to set options or perform any extra configuration to collect them.

Monitoring Service Levels

System metrics are available in Fusion Middleware Control for system components within a given Oracle Business Intelligence installation. If you encounter a problem, such as an application that is running slowly or is hanging, then you can view more detailed performance information to learn more information about the problem. You can use WSLT commands to periodically save metric information to a file so that you have a record of past metric values. See "DMS Custom WLST Commands" in

Oracle Fusion Middleware WebLogic Scripting Tool Command Reference for more information.

You can also view metrics for Java components using the Oracle WebLogic Server Administration Console.

This section contains the following topics:

■ Section 7.1.1, "Using Fusion Middleware Control to View Common Performance Metrics"

■ Section 7.1.2, "Using Fusion Middleware Control to View All Oracle Business Intelligence Metrics"

■ Section 7.1.3, "Using the Administration Console to View Metrics for Java Components"

7.1.1 Using Fusion Middleware Control to View Common Performance Metrics

You can access the most commonly viewed performance metrics from the Metrics tab of the Capacity Management page.

To use Fusion Middleware Control to view common performance metrics:

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."