|
Oracle® Business Intelligence Server Administration Guide > Clustering Oracle BI Servers > Using the Cluster Manager >
Viewing and Managing Cluster Information
The section describes how to view status, cache, and session information about a cluster and the meaning of the information provided. Status Information
The Status view is automatically displayed when you first open the Cluster Manager window. You can also access the Status view by selecting View > Status in the Cluster Manager window. The categories of information displayed in the Information pane may vary depending on the server to which Administration Tool is connected. Table 35 describes categories that may appear.
Table 35. Status Columns
|
|
Last Reported Time |
The time the Cluster Controller or Oracle BI Server communicated with the Controlling Cluster Controller. If the server or controller is offline, this field may be blank. |
Name |
The name of the machine hosting the Oracle BI Server or Cluster Controller. |
Role |
The role of the object in the cluster: - Controlling. A Cluster Controller that is currently assigned the responsibility for control of the cluster.
- Primary. The primary Cluster Controller. This role is not displayed if the primary Cluster Controller is currently the controlling Cluster Controller.
- Secondary. The secondary Cluster Controller. This role is not displayed if the secondary Cluster Controller is currently the controlling Cluster Controller.
- Clustered server. An Oracle BI Server that is a member of the cluster. This role is not displayed for the clustered server defined as the master server.
- Master. The clustered server that the Administration Tool connects to for editing repositories in online mode.
- Active. The Scheduler is active.
|
Sessions |
This field is available when either Servers or an individual server is selected in the Explorer pane. It shows the number of sessions currently logged on to a clustered server. |
Start Time |
The timestamp showing when the Cluster Controller or Oracle BI Server was last started. This field will be blank if the Cluster Controller or clustered server is offline. |
Status |
The status of the object in the cluster: - Online. The Cluster Controller or Oracle BI Server is online. For Cluster Controllers, this means the controller can accept session requests and assign them to available servers within the cluster. For clustered servers, this means that the server may be assigned sessions by the Cluster Controller.
- Quiesce. This status is applicable to clustered servers only. This means that any activity in progress on outstanding sessions will be allowed to complete before the server transitions to Offline status.
- Offline. The Cluster Controller or Oracle BI Server is offline. For Cluster Controllers, this means the controller cannot accept session requests or assign sessions to available servers within the cluster. For clustered servers, this means that the server is not communicating with the controlling Cluster Controller and cannot accept sessions assigned by the controlling Cluster Controller. If the server subsequently becomes available, it will be allowed to participate in the cluster. If you want to stop the Cluster Controller or clustered server after quiescing it, you need to issue the Stop command.
- Forced Offline. This status applies to clustered servers only. The Oracle BI Server has been stopped. This is identical to the offline status, except that if the Oracle BI Server comes back online, it will not be assigned requests. The server will remain in this state until the Start command is issued against this server from the Administration Tool Cluster Manager or both Cluster Controllers are shut down and restarted.
- Online: Active. The Scheduler instance is online, running, and the one to which Scheduler clients will connect. This instance will execute jobs.
- Online: Inactive. The Scheduler is online but not running. This instance is ready to take over for the active instance if the active instance becomes unavailable.
- Online: Inactive Pending. The Scheduler was active and is trying to go into an inactive state. This might take a few minutes, for example, if a multiple jobs are running.
|
Type |
When Clusters is selected in the Explorer pane, this field is available. There are two types: - Controller. The object is a Cluster Controller.
- Server. The object is an Oracle BI Server.
- Scheduler. The object is a Scheduler Server.
|
Cache Information
The Cache view is available in the Cluster Manager window if caching is enabled. The categories of information and their display sequence are controlled by your Options settings. Table 36 describes categories that may appear.
Table 36. Cache View Columns
|
|
Business Model |
Name of the business model associated with the cache entry. |
Column count |
Number of columns in each row of this cache entry's result set. |
Created |
Time the cache entry's result set was created. |
Creation elapsed time |
Time, in milliseconds, needed to create the result set for this cache entry. |
Full size |
Full size is the maximum size used, considering variable length columns, compression algorithm, and other factors. The actual size of the result set will be smaller than Full size.me, in seconds, needed to create the result set for this cache entry. |
Last used |
Last time the cache entry's result set satisfied a query. (After an unexpected shutdown of an Oracle BI Server, the Last used time may temporarily have a stale value, that is, older than the true value.) |
Row count |
Number of rows generated by the query. |
Row size |
Size of each row (in bytes) in this cache entry's result set. |
SQL |
Text of the SQL that generated the cache entry. |
Use count |
Number of times this cache entry's result set has satisfied a query (since Oracle BI Server startup). |
User |
ID of the user who submitted the query that resulted in the cache entry. |
To view cache information
- Click an individual server in the Explorer pane, and then select View > Cache.
Session Information
The Session view is available for Oracle BI Servers. The information is arranged in two windows, described in Table 37. - Session window—Appears on the top. Shows users currently logged on to the Oracle BI Server.
- Request window—Appears on the bottom. Shows active query requests for the user selected in the Session window.
Table 37 describes the information that appears in the Session window.
Table 37. Session Window Columns (Top Window)
|
|
Catalog |
Name of the Presentation layer catalog to which the session is connected. |
Client Type |
Type of client session. The client type of Administration is reserved for the user logged in with the Oracle BI Administrator user ID. |
Last Active Time |
Timestamp of the last activity on the session or the query. |
Logon Time |
Timestamp when the session logged on to Oracle BI Server. |
Repository |
Logical name of the repository to which the session is connected. |
Session ID |
Unique internal identifier that the Oracle BI Server assigns each session when the session is initiated. |
User |
Name of the user connected. |
Table 38 describes the information that appears in the Request window.
Table 38. Request Window Columns (Bottom Window)
|
|
Last Active Time |
Timestamp of the last activity on the session or the query. |
Request ID |
Unique internal identifier that the Oracle BI Server assigns each query when the query is initiated. |
Session ID |
Unique internal identifier that 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 may 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 kill a request, select it and click the Kill Request button. The user will receive an informational message indicating that the Oracle BI Administrator cancelled 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.
|
To manage clustered servers
- In the Explorer pane, click the plus sign (+) to the left of the Server icon to display the servers in the cluster.
- In the Information pane, select a server.
- Select Action, and then select one of the available options.
When the operation finishes, the status of the clustered server will be refreshed automatically.
To view session information
To disconnect a session
- In the Session view, right-click the session in the Session window (top window) and click Disconnect.
To kill a query request
- In the Session view, right-click the request in the Request window (bottom window) and click Kill Request.
Server Information
Selecting Server info from the View menu provides information about the cluster server such as server version number.
|
