New OBIEE Tuning Guide (Version 4) – released Jan 2014

A new version of the OBIEE Tuning Guide (Version 4) was released in January, 2014.  It is suitable for OBIEE and versions.

It can be found on Oracle Support under Document ID 1333049.1.   Or here is a direct link to the document (PDF).


New highlights from the previous document include:

  •     Optimized JVM switches for JRockit / Sun JVM / IBM JVM
  •     New tuning parameters settings / values for JavaHost / OPIS / OBIS components.
  •     Improved performance monitoring techniques.
  •     IBM WebSphere tuning parameters.
  •     More WebLogic Server tuning parameters.
  •     Windows Server 2012 tuning parameter.
  •     New optimized Linux / AIX tuning parameters.
  •     Additional Essbase ASO tuning parameters.
  •     libOVD authenticator search tuning


As always, this document provides us with recommended baselines or starting points, but the appropriate settings for each environment will vary.


Weird prompt values in dashboard prompts after upgrade

Have you noticed weird prompt values in your reports after upgrading OBIEE from 10g to 11g?  Below is an example of what you might see …


This is usually caused by calculated columns in the report.  You will need to remove those columns, and then add them back to the report.  And then, depending on what your calculated columns were being used for, you may want to consider using Selection Steps instead to accomplish the same logic.

If you know of another way to fix this scenario, please share.

Setting up Putty to display screens on your desktop for installing or upgrading OBIEE 11g on Linux

When you attempt to run the RCU (Repository Creation Utility) or UA (Upgrade Assistant) scripts from your desktop/laptop using Putty for an OBIEE install or upgrade on a Linux server, you may get the following error …

UPGAST-00107: The DISPLAY environment variable is not set. The graphical user interface (GUI) requires that this environment variable be set on UNIX.

If you get this error, this post may help you to solve it.  You need to do some configuration in Putty.

Open Putty.


Select the server that you want to configure from your list of servers. You will notice that the values get populated into the fields.


Expand SSH, the select X11.   Then Check “Enable X11 forwarding” checkbox, and enter “localhost:0.0” in the X display location box.


Do not click open at this point.

Go back up and click on Session in the left menu.

And then Save.

However, before you connect using Putty, you should run Xming.

Start -> All Programs -> Xming -> Xming

[If you do not have Xming, you can download it for free, then install it.]


Now when you open Putty and connect to your server, you should be able to run the install or upgrade processes and see the wizard screens for each step, for example …

>  ./ua   (run the UA script, then the wizard screen will appear)


UPGAST-00014 error when upgrading OBIEE 10g RPD and Catalog to 11g

If you get this error during Step 4 of the Upgrade Assistant for upgrading OBIEE 10g RPD and/or Catalog to 11g, then this post might be helpful.

UPGAST-00014: unable to connect to WebLogic Server at localhost:7001
t3://localhost:7001: Destination unreachable; nested exception is: Connection refused; No available router to destination


Perform the following steps that may resolve your problem:

– Log in to Administration Console.  http://yourserver:7001/console
– Click the ‘Servers’ link.


Then in the Summary of Servers page / Configuration tab, click ‘AdminServer(admin)’.


– From the Settings for AdminServer page, select the ‘Protocols’ tab, then the ‘Channels’ subtab.
– And then Click ‘Lock & Edit’ button in the upper left Change Center.


– Click the New button to begin creating a new Network Channel.
– Enter the following information…
Name: Loopback (or whatever name you like)
Protocol: t3

– The click Next


– The enter …
Listen Address: localhost
Listen port: 7001
Click Finish


The new Network Channel (Loopback) is added.  Activate the changes by clicking on the “Activate Changes” button.


Now, retry running the Upgrade Assistant. There is no need to restart any of the services. 
You should now get past Step 4 (the point at which you were getting the error before).

Unable to see Administration link or dashboards with Administrator ID in OBIEE 11g

If you are unable to see Dashboards or the Administration link after logging in with the administrator ID in OBIEE 11g after upgrading from 10g, this post may help.

Log in to Analytics — http://yourserver:9704/analytics

Manually change URL by attaching “saw.dll?Managegroups” to the end after analytics, so it looks like this … http://yourserver:9704/analytics/saw.dll?Managegroups


Select the “Presentation Server Administrators” catalog group and Edit


Add the “BI Administrator Role” Application Role by selecting it in the left and using the arrows to move it to the right.


Log out and log back in with the Administrator ID.

You should now be able to see the “Administration” link at the top right, and also be able to see the dashboards that you had access to by clicking or mousing-over the Dashboards link/dropdown.


‘No fact table exists at the requested level’ error in OBIEE 11g

If you receive an error like this when you attempt to run a report, this post might help you.  This is an error that may occur after upgrading from OBIEE 10g to 11g.

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail:

Check each column used in your report and each column used in the filter definition to ensure that they are referencing the correct table.

A likely cause of this error is that one or more of your select columns or filter columns is referencing a column in a different subject area that the one being used in your report (different from the one you intended).

OBIEE 10g was more forgiving than 11g – and maybe fortunately, so that errors like these do not go unnoticed/undetected.

Data type related error in OBIEE 11g – Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P

If you receive an error like this in OBIEE 11g, this post may help you resolve the problem.  This is an error that you may get after upgrading from OBIEE 10g to 11g.

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 59140] The evaluation of the index 11 expression on row count -1 failed. [nQSError: 59001] Binary Logical operation is not permitted on VARBINARY, INTEGER operand(s). (HY000)


OBIEE 10g is a lot more forgiving than 11g.  So what worked in 10g may not work in 11g – such as data type mismatches.  For this error, you need to check the data types of your columns and the data types of the values being used in your column calculations.

For example, you may have a column formula like this …

sum(case when “Table”.”Column”=3 then 1 else 0 end)

Note the column is being used like an INTEGER. This worked in 10g, but does not in 11g.

When you check the data type in your RPD, it may show that the column is a VARCHAR.  You then will need to put quotes around the value (the ‘3’) … like this …

sum(case when “Table”.”Column”=’3’ then 1 else 0 end)

This should hopefully solve the problem.