Oracle Tech Help – OBIEE 12c Installation Prerequisites

Oracle Tech Help – OBIEE 12c Installation Prerequisites

If you are planning to install OBIEE 12c, there are some key prerequisites that you’ll need complete to ensure the process goes smoothly. In this blog, we will go through the steps of the prerequisites checks needed when installing OBI 12c in Solaris/Linux. We will also discuss a few issues which you’ll face during installation, as well as the required fixes for the installation to complete successfully.

Every Oracle software installation is required to pass a set of prerequisite checks related to operating system version, java version, database version, if required, and any related middleware or infrastructure applications which are interlinked to the software installed.

Ok, the first step is to look at the proper OBI software certificate matrix located at https://support.oracle.com.   You’ll need to enter some basic information related to the OBI software version. In the example below, I entered OBI release 12.2.1.3 which yielded the following results related to OS, Databases, Desktop Apps and Development tools.

 

 

You can also find the related certification matrix spreadsheet on the Oracle website related to the OBI software which you are installing.

Once you have that information, the next step is to verify the operating system of the server where you will be installing the OBI 12c software.

You’ll need to use the following commands to determine OS type and version.

Uname                        -provides OS

uname -a                    -provide the OS/OS version/Kernel/32 bit or 64 bit

cat /etc/release        -provides the details of the whole operating system.

 

Based on the appropriate operating system version, you’ll need to download the proper version of OBI 12c software from Oracle.com or https://edelivery.oracle.com . You’ll need to have the following software to get started:

  • Java (JDK version based on the certification matrix)
  • x.x.x_infrastructure.jar
  • x.x.x.bin
  • x.x.x-2.zip

You will need to download JDK 1.8+(or later) based on the OS we are using. The next step is to copy it to your server.

Install the JDK by logging as root user and set the paths in .bash_profile (or whatever shell you are using) as noted below.

export JAVA_HOME= /java/jdk1.8.x_xx

export PATH=$JAVA_HOME/bin:$PATH

Then you’ll create a proper folder structure for OBIEE in Linux/Solaris for ease of use Oracle_Home (this is where whole OBIEE files present) and update the bash_profile for Oracle_Home.

app/OBIEE/Middleware/Oracle_Home

ORACLE_HOME= app/OBIEE/Middleware/Oracle_Home; export ORACLE_HOME.

At last, you’ve reached the fun part. Finally, start the OBI 12c installation tasks as follows: Fusion Middleware

java -d64 -jar fmw_12.2.x.x_infrastructure.jar

Note: During this installation, the software will check for prerequisites.  It should pass if it meets all the required system certifications. If it fails, you’ll need to re-check all the prerequisites once again. This should complete the WebLogic setup.

OBIEE 12c needs to be installed

./bi_platform-12.2.x.x_.bin

After successfully installing of OBIEE, you’ll need to install RCU for OBIEE metadata tables in the provided database.

cd  $oracle_home/oracle_common/bin

./rcu

-After completion of RCU, you need to configure OBIEE, as follows:

cd $oracle_home/bi/bin

./ config.sh

Once OBIEE is installed,  you’ll need to setup few paths for OBIEE and LD_LIBRARY_PATH into bash_profile for OBIEE to function properly during start and stop of the system.

LD_LIBRARY_PATHFunctionEnvironment variable to specify the path used to search for libraries on UNIX and Linux. The environment variable may have a different name on some operating systems, such as LIBPATH on AIX, and SHLIB_PATH on HP-UX.
PATHFunctionUsed by the shell to locate executable programs; must include the $ORACLE_HOME/bin directory.

Source for definition: oracle.com

 

Additionally, you will need to set below PATH:

LD_LIBRARY_PATH=<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/8.0.1/lib:<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib:<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/7.1.4/lib:<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/5.3/lib:<ORACLE_HOME>/oracle_common/jdk/jre/lib/amd64/server:<ORACLE_HOME>/oracle_common/jdk/jre/lib/amd64:<ORACLE_HOME>/bi/bifoundation/server/bin:<ORACLE_HOME>/bi/bifoundation/web/bin:<ORACLE_HOME>/bi/clients/Essbase/EssbaseRTC/bin:<ORACLE_HOME>/bi/lib:<ORACLE_HOME>/lib:<ORACLE_HOME>/oracle_common/adr:<ORACLE_HOME>/oracle_common/lib:/usr/lib:/libLD_LIBRARY_PATH_64=<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/8.0.1/lib:<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/7.1.5/lib:<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/7.1.4/lib:<ORACLE_HOME>/bi/modules/oracle.bi.datadirect.odbc/5.3/lib:<ORACLE_HOME>/oracle_common/jdk/jre/lib/amd64/server:<ORACLE_HOME>/oracle_common/jdk/jre/lib/amd64:<ORACLE_HOME>/bi/bifoundation/server/bin:<ORACLE_HOME>/bi/bifoundation/web/bin:<ORACLE_HOME>/bi/clients/Essbase/EssbaseRTC/bin:<ORACLE_HOME>/bi/lib:<ORACLE_HOME>/lib:<ORACLE_HOME>/oracle_common/adr:<ORACLE_HOME>/oracle_common/lib:/usr/lib:/lib

MW_HOME=<ORACLE_HOME>

BI_PRODUCT_HOME=<ORACLE_HOME>/bi

DOMAIN_HOME=<ORACLE_HOME>/user_projects/domains/bi

 

Of course, sometimes things go wrong during installation.  Here are some of the common issues you may face and how to resolve them.

Common Issues faced while installation of OBIEE 12c due to prerequisites:

  • Issue related to operating system not certified

Error Code: Checking operating system certification; warning sign next to it.

 

Fix: Something is not right with OBIEE software being installed. We need to re-check the certification matrix and download correct OBIEE software for the operating system version we have.

  • While running config.sh (configuration of OBIEE Domain and Ports). BI Startup does not complete successfully, and it throws below error.

Error code: Config Action BI Startup failed

Configure BI Failed with Execution of [start.sh] failed with exit value 1


Node manager does not start using start.sh command
:

You may find a few errors in OBIS log related to missing library files such as:

saw server: fatal: libperfapi64.so: open failed: No such file or directory and libnqportable64.so: open failed: No such file or directory.

Fix: You need to add LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 paths provided above to bash or shell profile. Which will be used by OBIEE when we start the entire domain using start.sh command.

And there you have it! You should be on your way to a successful OBI 12c installation.  As we all know, these installs can be tricky at time, but as long as you follow the steps as outlined here, you should be good to go!

 

 

Tags:

Write a Comment

x

Contact Us Close