Thursday, March 28, 2013

Clustering 10G

Clustering Active-Active on AIX ( OBIEE 10g)

The Oracle Business Intelligence components can be installed in a distributed architecture in a multi-server environment. Oracle Business Intelligence provides for high availability through the use of native clustering, fail over  and load balancing capabilities. The Oracle Business Intelligence SSL Everywhere feature allows you to secure communications across all Oracle Business Intelligence components. Oracle Business Intelligence allows you to enable Single Sign-On for your deployment. The Oracle Business Intelligence infrastructure allows integration with the Oracle Middle ware products such as Oracle Internet Directory and Oracle Single Sign-On.

Cluster Architecture:

Installation of Oracle BI Components

Refer to the Oracle Business Intelligence Infrastructure Installation and Configuration Guide for
information on required third-party software, pre-requisites and installation requirements for
AIX platforms.

Note Pre-Requisites:-

1 .All BI Servers participating in the cluster need to be within the same domain and on the same LAN.
2. The clock on each server participating in a cluster must be kept in synchronization.

Presentation Catalog:
Create a network share for the Presentation Catalog. All instances of BI Presentation Services in the cluster must have read and write access to this share.

-Place the Presentation Catalog on the network share.

- Reference the shared Presentation Catalog as \\satya\OracleBIData\web\catalog\Catalog 

Name, where “CatalogName” an example of the catalog name.

Repository Publishing Directory

- Create a shared directory for the Repository Publishing Directory. The Master BI Server must have read and write access to this directory. All other BI Servers must have read access.
-Reference the shared network share for the Repository Publishing Directory

Cluster-Aware Cache

>Create a shared directory for the global cache. All BI Servers must have read and write access
to this directory.

>Reference the shared global cache as \\satya\OracleBIData\ClusterCache.

Scheduler Scripts

>Create network shares for the Scheduler scripts. The Scheduler servers must have read and write access to this share.

>Reference the shared Scheduler scripts as \\satya\OracleBI\Server\Scripts\Common and \\satya\OracleBI\Server\Scripts\Scheduler.

>Copy default and custom Scheduler scripts from to the corresponding network shares created for the Scheduler scripts.

Configuration of OBIEE Components for Clustering, Load Balancing, and Failover

>Use the procedures in this topic to configure the Oracle BI components for clustering, load balancing and failover.

Pre-Configuration Summary Tasks

>Before configuring the Oracle BI components for clustering and load balancing, perform the following tasks:

-Identify the Cluster Controller to serve as the Primary Cluster Controller.
For example, Server01.

-Identify the Cluster Controller instance to serve as the Secondary Cluster Controller. For example, Server02.

- Identify the BI Server instance to serve as the Master BI Server. For example, SERVER-01.

· Copy the repository file (RPD) to the machines hosting the BI Servers.

1) The repository file must be copied to OracleBI_HOME\server\Repository.

2) On Linux or UNIX, the file must be copied to OracleBI_HOME/server/Repository.

· Before performing the configurations, shut down all BI services or processes. Restart the BI 

services or processes after configuration is complete.

Setting Parameters in the NQSConfig.INI File :-

This topic shows how to use the NQSConfig.INI file to configure your deployment. 

The NQSConfig.INI file is

located in following folders:

· Windows: OracleBI\server\Config

· Linux or UNIX: OracleBI/server/Config

Change parameters in the NQSConfig.INI file:

1) Open the NQSConfig.INI file for editing.

2) In the Repository section of the NQSConfig.INI, define your repository by setting the logical 

Repository name and file name pair. For example: Star = <>, DEFAULT;

3) Set Cache parameters. Caching is enabled by default.

To use the cluster-aware caching capability, set the cluster-aware cache parameters for the BI Sever. In the Query Result Cache section of the NQSConfig.INI file, uncomment and set thefollowing parameters:




4) In the Server Section, uncomment the parameter CLUSTER_PARTICIPANT and set it to YES.

5) When the BI Server is a cluster participant, comment out the parameter


6) Set the parameter RPC_SERVICE_OR_PORT to the desired port that the BI Server will listen on. The default port number is 9703.

7) In order for online modifications to be made to the repository, uncomment and set the following Parameters:



Here is the example:


Star = OBIEE.rpd, DEFAULT;



// Cluster-aware cache

GLOBAL_CACHE_STORAGE_PATH = “\\satya\OracleBI\ClusterCache” 700 MB;









Please looks like below screenshot.

Setting Parameters in the NQClusterConfig.INI File :-

This topic shows how to use the NQSClusterConfig.INI file to configure your deployment.
 The  NQSClusterConfig.INI file in following folders:

Windows: OracleBI\server\Config

Linux or UNIX: OracleBI/server/Config

Change parameters in the NQClusterConfig.INI file:

· Open the NQClusterConfig.INI file for editing.

· Change the parameter ENABLE_CONTROLLER to YES to enable clustering.

· Identify the Primary and Secondary Cluster Controllers:

1) Change the parameter PRIMARY_CONTROLLER to the machine hosting the Primary Cluster Controller.

2) Change the parameter SECONDARY_CONTROLLER to the machine hosting the Secondary Cluster Controller.

· Set the parameter SERVERS by entering a comma-separated list of the BI Server hostnames.

· Set the parameter MASTER_SERVER by entering the hostname of the Master BI Server machine.

· Set the parameter SCHEDULERS for the Scheduler servers participating in the cluster.

SCHEDULERS = “scheduler1:port”, “sscheduler2:port>:”; Default Port is 9705

Here is the sample nqclusterconfig.ini file:
SCHEDULERS = “SCHEDULER-01:9705:9708″,”SCHEDULER-02:9705:9708″;

Configuring BI Presentation Services :-

Oracle BI Presentation Services is configured by setting parameters in the configuration file instanceconfig.xml. The instanceconfig.XML file is located in the following directory:

Linux or UNIX: OracleBIData_HOME/web/config

Use the following procedure to configure BI Presentation Services on each machine that hosts BI Presentation Services:· Open the configuration file instanceconfig.xml for editing.· Locate the element. Configure for communication with the clustered Scheduler instances in Section Alerts:

ccsPrimary=”Server01″ ccsPrimaryPort=”9706″ ccsSecondary=”Server02″

· Under the ServerInstance tag, create the JavaHostProxy element.

· Set the JavaHostProxy element attributes and values to point to the Javahost cluster:

Where BI-Server01 and BI-Server02 are the machines that host the BI Javahost component.
 BI Javahost

was installed along with the installation of BI Presentation Services.
The Hosts element contains Host sub-elements that identify the Javahost and port pairs. (The default Javahost port is 9810.)

1) Use the values in the Port element in the config.xml file on the machine where Javahost
is installed.

2) The config.xml file is located in OracleBI_HOME\web\javahost\config (Windows) and
OracleBI_HOME/web/javahost/config (Linux).

· Modify the element to point to the shared Presentation Catalog:


· Under the ServerInstance element, create the Catalog sub-element with the following attributes and values:


Note: Insted of using'(' use'<' for above config lines.
These settings manage when BI Presentation Services cache is updated from disk in environments with multiple BI Presentation Services instances.
· Save changes to the file.

Configuring BI Scheduler on Linux or UNIX :-
The Scheduler configuration options are set using schconfig, a console-based application. On the machines where Scheduler instances are installed, in the directory OracleBI_HOME/setup, run the command schconfig:
· .
· schconfig

Here are the steps:
· From the Delivers Configuration choices that appear, select 1 – Configure Scheduler.
· For each Scheduler Configuration Menu choice shown in the following table, select the listed parameter and configure as shown.
· Select 0 to quit and save changes when prompted.
· Select 0 to quit the utility

Configuring BI Presentation Services Using J2EE :-

Follow the steps in this procedure to configure BI Presentation Services Plug-in to communicate with the multiple BI Presentation Services instances. For the Java servlet, configure the Plug-in in the web.xml file,

located in following directory:

Linux or UNIX: ORACLE_HOME/j2ee/bianalytics/applications/analytics/analytics/WEB-INF

Here are the steps:

· Open the web.xml file for editing.

· Locate the following param-name and param value pairs:


· Save changes to the file.

· Copy the web.xml file to  OracleBI_HOME/web/app/WEB-INF on Linux.

· Restart your Java Servlet container.

Modifying the odbc.ini file under Linux/UNIX :-

On Linux and UNIX machines, the odbc.ini file is located in the OracleBI_HOME/setup directory. Default Port is 9706

Here are the steps:

· Open the odbc.ini file for editing.

· Make the following modifications:







· Save changes to the file.

we have installed OBIEE for optimized availability in a clustered environment.


  1. The BI Cluster Server feature allows multiple BI Servers to be deployed. BI Schedulers participate in the cluster in an active passive configuration.
  2. A cluster-aware cache capability offers support for a common query cache that is visible to all BI Servers in the cluster. Clustering capability for the Presentation layer allows for the deployment of a multi-server environment to better manage large volumes of users and to provide high availability.
  3.  BI Presentation Services instance. Native load balancing and failover capabilities are offered for the components of the Presentation layer.
  4.   Multiple BI Presentation Services instances may be installed and configured to   participate in     the Oracle BI deployment to service a large volume of users and to provide for high availability.
  5. The Oracle BI Server maintains a local, disk-based cache of query result sets called the query cache. The query cache allows a BI Server to potentially satisfy many query requests without accessing back-end databases. This reduction in communication costs can dramatically decrease query response time.

Hope this help's

Satya Ranki Reddy

No comments:

Post a Comment