Importing data from Essbase cubes.

While using Oracle Essbase as your data source in OBIEE, there are some additional things that you need to configure before proceeding.

My previous article about "Setting Up Essbase Data Sources" will help to do this.

When you are done with this configuration steps, you are good to go with handling Essbase data source with OBIEE. But there's a problem if you don't know what are default port on which your Essbase data source is installed. If everything is installed on the default ports by your Admin, you are lucky enough; but unfortunately that's not the truth always. If it is not, you might get the following error message,

Essbase Error: 1030818: Login failed. Please check if server and port are correct. If you received timeout or handshake failure, please check if you tried to connect to secure port without secure keyword or clear port with secure keyword.

To get on which port your essbase can be accessible, you can follow the below steps.

• Open you easconsole
• http://Ess_Server:9704/easconsole
• Launch application.
• Put the credentials to connect your Essbase server.
• Expand Essbase servers.
• Select your particular Essbase server where your cubes are residing. (In my case, EssbaseCluster-1)

• Right click and go to Edit > Properties.

• Move to Environment tab.

You can use this AGENT PORT at the time of importing your cubes in OBIEE. Refer the following screenshot,

Happy stay.. :-)

Admintool could not load Essbase driver. Please check the configuration.

Problem:

On Windows systems, when we install Administration Tool from "client-only" installation, it can throw an error while import Essbase data source.

"Admintool could not load Essbase driver. Please check the configuration"

Cause:

The Oracle BI Server uses the Essbase client libraries to connect to Essbase data sources. You must ensure that the Essbase client libraries are installed on the computer running the Oracle BI Server before you can set up a connection to or import metadata from Essbase data sources. You also need to ensure that the Essbase client libraries are installed on any computer where you want to run the Administration Tool.

After you verify that the Essbase client libraries are installed on the appropriate computers, you must ensure that the PATH environment variable on each computer includes the location of the Essbase client driver (for example, EPM_ORACLE_HOME/products/Essbase/EssbaseClient)

You also need to ensure that an additional environment variable is set appropriately where Admin tool is installed.

Because, other system processes need the information contained in the environment variables set for the Essbase client libraries. The following sections provide additional information:

Solution:

On Windows systems, to enable connectivity, you need to update bi-init.cmd on each computer running the Administration Tool.

To add Essbase environment variables to bi-init.cmd:

C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client Tools\oraclebi\orahome\bifoundation\server\bin

Add a line setting the ESSBASEPATH or ARBORPATH environment variable, as appropriate for your version and installed location of the Essbase client libraries. 

For example:

set ORACLE_HOME=C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client Tools\oraclebi\orahome

set ORACLE_INSTANCE=C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client Tools\oraclebi\orainst

set ORACLE_BI_APPLICATION=coreapplication

set ESSBASEPATH=C:\Oracle\Middleware\EPMSystem11R1\common\EssbaseRTC-64\11.1.2.0

set ARBORPATH=C:\Oracle\Middleware\EPMSystem11R1\products\Essbase\EssbaseClient

Locate the line that sets the PATH environment variable, and add the location of the Essbase client binaries.

For example:

set PATH=%ORACLE_HOME%\bifoundation\server\bin;%ORACLE_HOME%\bifoundation\web\bin;%ORACLE_HOME%\bin;%JAVA_HOME%\bin;%windir%;%windir%\system32;%ESSBASEPATH%\bin;%ARBORPATH%\bin;%PATH%

Save and close the file.

Now you can open your Admin Tool & can try to import Essbase cubes,

Credits:

Tarun Kumar Swami. :-)