Friday, September 24, 2010

Essbase as a data source in OBIEE 10.1.3.4.1

I came across many resources on web about using Essbase as a data source in OBIEE but all the content is around configuring cube once the cube is imported into RPD. I had problems with OBIEE connecting to Essbase service and with no experience on Essbase, it just makes it difficult to debug where the problem is. Below is the error that I was getting.

Network error [146]: Unable to connect to [:1423]. The client timed out waiting to connect to Essbase Agent using TCP/IP. Check your network connections. Also make sure that server and port values are correct

The very fact that there is not much content on issues like this on web confirms my belief that there are not that many implementations hosted on Solaris. Anyway, here are the steps that should be followed to fix the issue, if the Essbase server installation is default installation. Essbase agent can be run on a different port; check with your Administrator or run netstat to identify what ports are used.

  1. Chcek what your Essbase server version is and install the same version of client on BI Server machine.
  2. Open port # 1423 (Essbase agent port) and port range 32768-33768 (ports on which Essbase clients connect to Essbase agent) in Essbase server for BI server to connect
  3. Run BI Server in 64-bit mode after adding environment variables that maintain paths to Essbase client. Changes in user.sh are pasted below.
  4. Import cubes in Admin Tool, check consistency and save the RPD
  5. Run Answers reports and validate data.
OBI uses client libraries to connect to Essbase, which means client should be installed. Below is the list of variables that should be added to user.sh in //OracleBI/setup directory.

# Essbase Parameters
#---------------------------
ARBORPATH=/Essbase/EssbaseClient
ESSBASEPATH=/Essbase/EssbaseClient
HYPERION_HOME= (up to Hyperion directory)
ESSLANG=English_UnitedStates.Latin1@Binary
export ARBORPATH
export ESSBASEPATH
export HYPERION_HOME
export ESSLANG
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ARBORPATH/bin
export LD_LIBRARY_PATH
LD_LIBRARY_PATH_64=$LD_LIBRARY_PATH_64:$ARBORPATH/bin
export LD_LIBRARY_PATH_64
#---------------------------

Oracle created this as a documentation enhancement.

6 comments:

Anonymous said...

Hi Aneel Kanuri,

recently we upgrade DEV from OBIEE 10.1.3.3.3 to OBIEE 10.1.3.4.1 .... When we testing with QA (10.1.3.3.3) reports and Dash Boards, almost every report is same ,But some reports getting grand total wired,but their column values are same ...,, Is their any patch that need to apply for that.

Can you mail me ,if you have any solution for this issue. mail me @ kesa.santhosh@gmail.com

Changa Reddy said...

You may check metalink for some tags on Grandtotals and reporttotals. I don't think you need a patch. It could be adding a tag in instanceconfig.xml. Check metalink for the tag.

Milton said...

Hello. I was reading your note, I am employed at environment unix and do not find the file user.sh
Can You helpme with that.

Regards,
Milton

Milton said...

Hello.
I was reading your note, I am employed at environment unix and do not find the file user.sh
Can You helpme with that.

Regards,
Milton

Milton said...

Hello. I was reading your note, I am employed at environment unix and do not find the file user.sh

Can You help with that.

Regards,
Milton

Anonymous said...

Hello. I was reading your note, I am employed at environment unix and do not find the file user.sh

Can You help with that.

Regards