Configuring Essbase Cluster for Fusion Applications

Introduction

This blog will provide you with some additional information regarding the configuration of Essbase to work with Fusion Applications (FA), especially if you have provisioned an FA environment using Release 3 (11.1.3) or Release 4 (11.1.4) and followed Chapter 14 of the Enterprise Deployment Guide to cluster BI and Essbase.  You may need to additional configuration and must contact your administrator, and then manually run this program, otherwise posting will fail:

Cannot connect to olap service.
Cluster name specified [Essbase_FA_Cluster] is invalid.
Releasing Root AM…

Main Article

The extra configuration is required becuase of  way Fusion Middleware Control edits the EPM System Registry during the HA configuration. During provisioning, a cluster with name Essbase_FA_Cluster is created and Essbase Server instance is attached to it as the child component. During the HA configuration, FMW Control creates another cluster – essbasecluster1 – and re-associates the existing Essbase Server instance as well as the passive failover instance to it as child component. Since FA uses Essbase_FA_Cluster, it is unable to get a connection as there are no child components to route the request. This can be viewed from the EPM system registry.EPM System registry can be viewed or modified using the epmsys_registry.sh which is located in CONFIG_TOP/BIInstance/config/foundation/11.1.2.0

Here CONFIG_TOP is the Local Application Configuration Directory specified during provisioning. If you chose not to Enable Local Application Configuration, then the shared Application Configuration Directory is used instead. Here is a screenshot of Installation Location screen of the provisioning wizard where these locations are specified:

01_Installation_Location

To view cluster configuration, use the following command:

epmsys_registry.sh view CLUSTER

Clusters before HA configuration:

COMPONENTS MATCHING THE TREE EXPRESSION

COMPONENT – 1
NAME –  Essbase_FA_Cluster
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ff5
TYPE –  CLUSTER
HOST –  bihost01-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
version = 11.1.2.0
instance_home = /u01/oracle/config/BIInstance
clusterType = standalone
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  HOST:bihost01-i.mycompany.com
ID –  d2a1f7ab4f4979dbS4559152b1382459fbf8S8000
TYPE –  HOST

Parent 2
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

CHILD COMPONENTS –

Child 1
NAME –  essbaseserver1
ID –  d2a1f7ab4f4979db380efec51385c4e8826S8000
TYPE –  ESSBASE_SERVER

Clusters after HA configuraion:

COMPONENTS MATCHING THE TREE EXPRESSION

COMPONENT – 1
NAME –  essbasecluster1
ID –  d2a1f7ab4f4979dbS1d0d6c591385c4e5d13S8000
TYPE –  CLUSTER
HOST –  bihost01-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
instance_home = /u01/oracle/config/BIInstance
version = 11.1.2.1.0
clusterType = failover
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  HOST:bihost01-i.mycompany.com
ID –  d2a1f7ab4f4979dbS4559152b1382459fbf8S8000
TYPE –  HOST

Parent 2
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

CHILD COMPONENTS –
Child 1
NAME –  essbasecluster1-inst1
ID –  d2a1f7ab4f4979db380efec51385c4e8826S8000
TYPE –  ESSBASE_SERVER

Child 2
NAME –  essbasecluster1-inst2
ID –  d2a1f7ab4f4979db6abf687f1385c4ea429S8000
TYPE –  ESSBASE_SERVER

COMPONENT – 2
NAME –  Essbase_FA_Cluster
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ff5
TYPE –  CLUSTER
HOST –  bihost01-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
instance_home = /u01/oracle/config/BIInstance
version = 11.1.2.0
clusterType = standalone
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  HOST:bihost01-i.mycompany.com
ID –  d2a1f7ab4f4979dbS4559152b1382459fbf8S8000
TYPE –  HOST

Parent 2
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

CHILD COMPONENTS – NONE

COMPONENT – 3
NAME –  EssbaseCluster-1
ID –  47769a798ea26f66S55aaf22d1385c4121acS7ff7
TYPE –  CLUSTER
HOST –  bihost02-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
instance_home = /u01/oracle/config/BIInstance1
version = 11.1.2.0
clusterType = standalone
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

Parent 2
NAME –  HOST:bihost02-i.mycompany.com
ID –  47769a798ea26f66125f10a113852df4db2S7ff0
TYPE –  HOST

CHILD COMPONENTS – NONE

As you can see, Essbase_FA_Cluster defined in the registry is missing child components after the HA configuration.

You can edit the EPM System registry to add the additional configuration. The solution is to rename essbasecluster1 to Essbase_FA_Cluster. Since the name is already used, it will be a 2 step process. First, we’ll rename the existing Essbase_FA_Cluster to Essbase_Incorrect_Cluster and then rename essbasecluster1 to Essbase_FA_Cluster . Here is a sequence of steps to do that.   1. Shutdown BI Domain (all the managed servers and admin server) and BI OPMN instances. For more details, refer to the Fusion Applications Administration guide     2. Connect to the database and backup the following tables:     FUSION_BIPLATFORM.HSS_COMPONENT_TYPES

FUSION_BIPLATFORM.HSS_COMPONENT_TIERS
FUSION_BIPLATFORM.HSS_COMPONENT
FUSION_BIPLATFORM.HSS_COMPONENT_PROPERTY_VALUES
FUSION_BIPLATFORM.HSS_COMPONENT_FILES
FUSION_BIPLATFORM.HSS_COMPONENT_LINKS       3. Change directory to CONFIG_TOP/BIInstance/config/foundation/11.1.2.0. This is the location of epmsys_registry.sh which we will use to update the registry.   4. Rename Essbase_FA_Cluster’s name to Essbase_Incorrect_Cluster using the following command. Please make sure the value between “\#” and “/” is the actual ID for Essbase_FA_Cluster as viewed earlier (highlighted in bold):   COMPONENT – 2
NAME –  Essbase_FA_Cluster
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ff5
TYPE –  CLUSTER

./epmsys_registry.sh  updateproperty \#d2a1f7ab4f4979db20430b6f138245ad141S7ff5/@name Essbase_Incorrect_Cluster

The above command should all be in one line.   5. Rename essbasecluster1 to Essbase_FA_Cluster using the following command. Similar to the previous step, use the correct ID, this time the ID of essbasecluster1 as viewed earlier (highlighted in bold):

COMPONENT – 1
NAME –  essbasecluster1
ID –  d2a1f7ab4f4979dbS1d0d6c591385c4e5d13S8000
TYPE –  CLUSTER   ./epmsys_registry.sh  updateproperty  \#d2a1f7ab4f4979dbS1d0d6c591385c4e5d13S8000/@name Essbase_FA_Cluster   6. View the cluster information. This time, you should see something similar to the following:   epmsys_registry.sh view CLUSTER   COMPONENTS MATCHING THE TREE EXPRESSION

COMPONENT – 1
NAME –  Essbase_FA_Cluster
ID –  d2a1f7ab4f4979dbS1d0d6c591385c4e5d13S8000
TYPE –  CLUSTER
HOST –  bihost01-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
instance_home = /u01/oracle/config/BIInstance
version = 11.1.2.1.0
clusterType = failover
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  HOST:bihost01-i.mycompany.com
ID –  d2a1f7ab4f4979dbS4559152b1382459fbf8S8000
TYPE –  HOST

Parent 2
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

CHILD COMPONENTS –

Child 1
NAME –  essbasecluster1-inst1
ID –  d2a1f7ab4f4979db380efec51385c4e8826S8000
TYPE –  ESSBASE_SERVER

Child 2
NAME –  essbasecluster1-inst2
ID –  d2a1f7ab4f4979db6abf687f1385c4ea429S8000
TYPE –  ESSBASE_SERVER

COMPONENT – 2
NAME –  Essbase_Incorrect_Cluster
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ff5
TYPE –  CLUSTER
HOST –  bihost01-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
instance_home = /u01/oracle/config/BIInstance
version = 11.1.2.0
clusterType = standalone
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  HOST:bihost01-i.mycompany.com
ID –  d2a1f7ab4f4979dbS4559152b1382459fbf8S8000
TYPE –  HOST

Parent 2
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

CHILD COMPONENTS – NONE

COMPONENT – 3
NAME –  EssbaseCluster-1
ID –  47769a798ea26f66S55aaf22d1385c4121acS7ff7
TYPE –  CLUSTER
HOST –  bihost02-i.mycompany.com
HYPERION HOME –  /u01/oracle/products/fusionapps/bi
PROPERTIES –
instance_home = /u01/oracle/config/BIInstance1
version = 11.1.2.0
clusterType = standalone
FILES – NONE
PARENT COMPONENTS –

Parent 1
NAME –  ESSBASE_PRODUCT
ID –  d2a1f7ab4f4979db20430b6f138245ad141S7ffb
TYPE –  ESSBASE_PRODUCT

Parent 2
NAME –  HOST:bihost02-i.mycompany.com
ID –  47769a798ea26f66125f10a113852df4db2S7ff0
TYPE –  HOST

CHILD COMPONENTS – NONE   7. Start BI Domain (including the admin server and managed servers) and BI OPMN managed Instances.

FA Jobs and programs should have no issues connecting to Essbase now!

Add Your Comment