Calculated Percentage Column always showing result as 0% Zero Percentage in OBIEE 11g

You may also face similar issue while upgrading OBIEE to a newer version or if you upgrade some of your dashboards from OBIEE 10.1.3.4 to 11.1.1.5. The issue is that, some of the calculations under certain columns in the reports were showing zeros instead of the calculated values.  The requirement was to calculate a match rate % for some data based on another field that showed 'MATCH' or 'NO MATCH'. 

 The real-time scenario was

(SUM(CASE Table1.Column1 WHEN 'MATCH' THEN 1 ELSE 0 END)/COUNT(Table1.Column1))*100

However, this was returning 0% as the result. With the help of some blogs and questions raised on OBIEE threads I came to know that this happens when you have an integer in a calculation. The solution which I used is very simple and was successful in achieving the requirement. The very easy fix to this issue is to multiply the calculation by 1.0.  The updated calculation which works is shown below and provides a meaningful result.

(don't use 1, as this will not work.  Use 1.0)

((1.0*SUM(CASE Table1.Column1 WHEN 'MATCH' THEN 1 ELSE 0 END))/(1.0*COUNT(Table1.Column1)))*100

Upgrade OBIEE 10g to OBIEE 11g

What happens during 10g upgrade to 11g?

By default, existing users and groups migrated to embedded WLS LDAP. Existing groups are automatically mapped to an Application role.

10g catalog groups are automatically migrated in the upgraded catalog and assigned the same privileges, access, and membership.

“Administrator” user automatically added as member of “BIAdministrators” group in embedded WLS LDAP and granted Administrator role. The user specified during OBIEE 11g installation (i.e. “weblogic”, “biadmin”) is also a member of the BIAdministrators group.

Prompted to set a repository password while running the upgrade assistant. Do not lose this password as there is no feature to recover a lost password.

Upgraded RPD will continue to point to 10g LDAP or external tables. Initblocks may need to be modified to ensure that deprecated, or reserved word, variable names are renamed. NOTE: If you intend to use another LDAP server, such as Oracle Identity Management (OID), then you must upgrade to the embedded LDAP server first, then migrate to the production LDAP server.

Existing groups will be migrated. Recommendation is to use application roles instead. Privileges on catalog objects may be granted to an application role via BI Presentation server Administration link.

Upgraded 10g RPD will point to external tables. Initblocks may need to be modified to ensure that deprecated, or reserved word, variable names are renamed.

“Everyone” group migrated to AuthenticatedUser role.

OBIEE 10g Production Installation Steps and Screenshots

Hi Friends,

Here I am giving you the production installation steps of OBIEE 10g.See the trivial installation steps of OBIEE,if you require that type of setup. The OC4J container installed,by default uses port 9704. For a production install we should have an application server and set the port to a standard port setting.

• Open a web browser and navigate to http://server name:9704/analytics
• The Login Screen will appear as below. Provide the username and password.The default administrative username and password is Administrator / Administrator.

 

• The Default Dashboard will appear as given below.

The default private dashboard for Administrator contains no content. There are shortcut links across the top and we can modify the dashboard with the "Page Options" dropdown.

Our OBIEE installation is finished and will function correctly.

OBIEE 10g Installation Steps with Screenshots

Hi Friends,

Sorry for being late to post OBIEE 10g Installation Steps.I was preparing note on detailed steps & screenshots with prerequisites for installation and steps for testing our installation.I hope this post will be very much useful to you.Don’t forgot to leave your comments and feedback.

Prerequisites

1. Windows XP
2. Current version of the Java JDK(Java Development Kit)

The JDK is required. The JRE(Java Runtime Environment) will not work.

Install Steps

• Unzip Install Media
• Execute Install Program 
• Accept Security Warning

• OBIEE Install Wizard Starts.It initializes and shows the required diskspace for  installing OBIEE.

• Verify Requirements. Click Next to Proceed.

• For the trivial install(It is the easiest to configure, smallest footprint install for any given version) we accept the defaults for install location. For installation type accept the default of basic. Click Next.

• Choose Setup Type that best suits your needs.If you are installing for the first time then, Select the complete installation and Click Next.

• Select JDK and enter OC4J Password

For this we need to browse and select the location where we have installed the Java JDK. Enter a password for the oc4jadmin user. Note this password on installation worksheet.

• Windows Services Setup 

Accept the defaults as it is and click Next.This will cause the BI Server to be started automatically on reboot.

• Select the language you prefer. Click Next

• Review the location where OBIEE 10x will be installed and list of components/features to be installed. Click next to proceed.

• Get a Message Regarding Installing .NET?
• The installation proceeds

• Success Screen

• More Success.This will show the summary of installation.
  Our OBIEE installation is finished and will function correctly after reboot.

• Reboot Required.

Testing Installation

We should see this screen at startup/login.

• The OC4J Startup Window

When we reboot or the user who have installed using this method logins, the OC4J container will be started. This means that when the user logs out,the OBI will no longer be accessible to users on the network. This is one of the reasons this is a trivial install not a production install.

See the production install instructions ,if you require that type of setup.