Status Information Viewing and Managing Cluster Information

6-12 System Administrators Guide for Oracle Business Intelligence Enterprise Edition To manage clustered servers: 1. In the Explorer pane, expand the Server icon to display the servers in the cluster. 2. In the Information pane, select a server.

3. Select Action, and then select an option.

When the operation finishes, the status of the clustered server is refreshed automatically. To view session information: 1. Select a server in the Explorer pane, and select View, then Sessions. Session information for the server is displayed in the Information pane. It shows all users logged into the server and all current query requests for each user. To disconnect a session: 1. In the Session view, right-click the session in the Session window top window and click Disconnect. When you disconnect a session, the ODBC session is terminated. Client users who were connected over this session receives errors if they attempt to run queries. Users must log out, then log back in again to start a new session. To terminate a query request: 1. 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 Column Description 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: options cifs.ntfs_ignore_unix_security_ops on