Wednesday, 1 May 2013

Oracle BI 11g – How to import Essbase cubes with BI Admin Tool 32 bit & 64 bit

I have seen many OBIEE consultants facing issue/errors while importing Essbase cubes with BI Client Tool. I have came across a very good write up from one of my Oracle colleague about some configuration hints to help to resolve this essbase import issue.

This blog is an attempt to share configuration tips to wider audience those who involved in the importing Essbase cubes with BI Client Tool and build metadata for MDX access store. The blog is meant to cover 32 bit and 64 bit Admin Tool Essbase access issue.

Installation of Essbase Client
Essbase Client installation is a must to use Essbase as data source. 

Download Location - http://edelivery.oracle.com

Essbase Installable(s)

·         Oracle Hyperion Enterprise Performance Management System Installer, Fusion Edition Release 11.1.2.1.0 for Microsoft Windows (64-bit)
·         Hyperion Enterprise Performance Management System Foundation Services Release 11.1.2.1.0 for Windows 64-bit, Part 1 of 7
·         Oracle Essbase Clients Release 11.1.2.1

Unzip the downloaded files into a single directory ( e.g. D:\emp11) and run installtool.cmd to start installation

Select Language – English
Welcome – Welcome to EPM System Installer
Destination – Enter Location for Middleware to install – c:\Middleware\Essbase
Installation Type – Choose Components Individually
Product Selection – Choose Essbase Client




Confirmation – Click Next to Confirm – Installation Complete

Environment Settings for Admin Tool
Once Essbase Client Installation is done the next step is to set or verify the environment variables.

Admin Tool 32 Bit
ESSBASEPATH

Set ESSBASEPATH as Windows system environment variable, this should be Essbase Client Install Path 
e.g.
ESSBASEPATH= D:\Middleware\Essbase\EPMSystem11R1\common\EssbaseRTC\11.1.2.0

PATH

The PATH windows system environment variable should have Essbase binaries path included
E.g
PATH =D:\Middleware\Essbase\EPMSystem11R1\common\EssbaseRTC\11.1.2.0\bin

Modify bi_init.bat

The location of file bi_init.bat depends on OBIEE client installation directory
D:\BI11gAdmin\oraclebi\orahome\bifoundation\server\bin

rem @echo off
set ORACLE_HOME=D:\ BI11gAdmin\oraclebi\orahome
set ORACLE_INSTANCE=D:\ BI11gAdmin\oraclebi\orainst
set ORACLE_BI_APPLICATION=coreapplication
rem call %ORACLE_INSTANCE%\bifoundation\OracleBIApplication\%ORACLE_BI_APPLICATION%\setup\user.cmd
set ESSBASEPATH=C:\Middleware\Essbase\EPMSystem11R1\common\EssbaseRTC\11.1.2.0
if NOT "%1" == "" set COMPONENT_NAME=%1
set PATH=%ORACLE_HOME%\bifoundation\server\bin;%ORACLE_HOME%\bifoundation\web\bin;%ORACLE_HOME%\bin;D:\BI11gAdmin\jre\bin;%ORACLE_HOME%\bin;%ESSBASEPATH%\bin;D:\Middleware\Essbase\EPMSystem11R1\bin-32;%PATH%
if NOT "%2" == "" %2


Admin Tool 64 Bit
ESSBASEPATH

Set ESSBASEPATH as Windows system environment variable, this should be Essbase Client Install Path 
e.g.
ESSBASEPATH=D:\Middleware\Essbase\EPMSystem11R1\common\EssbaseRTC-64\11.1.2.0

PATH

The PATH windows system environment variable should have Essbase binaries path included
E.g
PATH = D:\Middleware\Essbase\EPMSystem11R1\common\EssbaseRTC-64\11.1.2.0\bin;

Modify bi_init.bat

The location of file bi_init.bat depends on OBIEE client installation directory C:\ORCL\BI11gAdmin\oraclebi\orahome\bifoundation\server\bin

rem @echo off
set ORACLE_HOME=D:\BI11gAdmin\oraclebi\orahome
set ORACLE_INSTANCE=D:\BI11gAdmin\oraclebi\orainst
set ORACLE_BI_APPLICATION=coreapplication
rem call %ORACLE_INSTANCE%\bifoundation\OracleBIApplication\%ORACLE_BI_APPLICATION%\setup\user.cmd
set ESSBASEPATH=D:\Middleware\Essbase\EPMSystem11R1\common\EssbaseRTC-64\11.1.2.0
if NOT "%1" == "" set COMPONENT_NAME=%1
set PATH=%ORACLE_HOME%\bifoundation\server\bin;%ORACLE_HOME%\bifoundation\web\bin;%ORACLE_HOME%\bin;D:\BI11gAdmin\jre\bin;%ORACLE_HOME%\bin;%ESSBASEPATH%\bin;D:\Middleware\Essbase\EPMSystem11R1\bin;%PATH%
if NOT "%2" == "" %2


Don’t forget to save changes, after this modification one should be able to import Essbase cubes with BI Admin Tool

I hope you find this configuration note useful. Copy and Share with proud :-)

No comments:

Post a Comment