OBIA 11.1.1.10.

1 Installation and configuration

steps

Below is the flow of installation

1. Installation of oracle database 12.1.0.2

2. Installing/upgrading Java
3. Creating RCU schema for OBIEE 11.1.1.9.0
4. Installing OBIEE 11.1.1.9.0
5. Installing ODI 11.1.1.9.0(Skip configuration)
6. Creating RCU schema for OBIA
7. Installing OBIA 11.1.1.10.1
8. Applying patches
9. Configuring OBIA 11.1.1.10.1
10. Creating ODI connection for master and Work repository
11. Setting up the source file location for ETL in ODI Studio.

Installation of oracle database 12.1.0.2

Finish the Pre-installation tasks for database installation

Copy the softwares to a hard disk

1. Create a directory on the hard disk, outside of the Oracle base directory, to hold
the Oracle software:

2. $ mkdir OraDb12c

3. Change the directory to the directory you created in Step 1:

4. $ cd OraDb12c

5. Mount the disk, if it is not mounted.

Some platforms automatically mount the disk when you insert it into the drive. If
the disk does not mount automatically, see the "Mounting Disks" section for
platform-specific information.
 6. Copy the contents of the mounted disk to the corresponding new subdirectory as
follows:

7. $ cp -R /directory_path OraDb12c

In this example, /directory_path is the disk mount point directory.

8. If necessary, mount the next disk and repeat Step 4.

Installing Oracle Database software

1. Log on as the Oracle software owner user (typically, oracle) to the computer on
which you want to install Oracle components.

2. If you are installing the software from installation media, mount the disk if it is
not mounted.

If the disk does not mount automatically, see the "Mounting Disks" section for
platform-specific information.

Some platforms automatically mount the disk when you insert the installation
media into the drive.

3. To start Oracle Universal Installer, complete one of the following steps depending
on the location of the installation files:

4. If the installation files are on installation media, enter commands similar to the
following, where directory_path is the path of the database directory on the
installation media:

$ /directory_path/runInstaller

If the installation files are on the hard disk, change the directory to
the database directory and enter the following command:

$ ./runInstaller

5. When the configuration assistant tasks are complete click finish, click Exit, then
click Yes to exit from Oracle Universal Installer.
 6. During the database installation, when Oracle Universal Installer prompts you to
run a script with root privileges, enter a command similar to the following in a
terminal where you are logged in as the root user, then click OK:

7. # /script_path/script_name

For more information see the description in the Install Product screen in the table
that follows.

8. See Chapter 7 for information about tasks that you must complete after you
install Oracle Database.

The following table lists the various screens displayed during an Enterprise Edition
installation for Oracle Database 12c:

Screen1: Configure Security Updates :-

Enter your email address, preferably your My Oracle Support email address or user
name in the Email field.

Select the I wish to receive security updates via My Oracle Support check box to
receive security updates.

Enter your My Oracle Support password in the My Oracle Support Password field.

Click Next.

Screen2 : Select Installation Option:-

Select one of the following installation options, and click Next:

Create and configure a database: This option creates a new database with
sample schemas.

Install database software only: This option only installs the database binaries. To
configure the database, you must run Oracle Database Configuration Assistant
after the software installation.

Upgrade an existing database: This option installs the software binaries in a new
Oracle home. After the installation, you can upgrade the existing database.

Screen3: System Class:-

Select the type of system for installing the database, and click Next.
 Desktop Class: Select this option if you are installing on a laptop or desktop class
system. This option includes a starter database and enables a minimal
configuration. This option is designed for those who want to get the database
running quickly.

See Also: "Setting the ORACLE_HOSTNAME Environment Variable"

Server Class: Select this option if you are installing on a server class system,
such as what you would use when deploying Oracle Database in a production
data center. This option provides more advanced configuration options. Advanced
configuration options available using this option include Oracle RAC, Oracle ASM,
backup and recovery configuration, integration with Oracle Enterprise Manager
Cloud Control, and more fine-grained memory tuning, among many others.

Screen4: Grid Installation Options:-

Select the type of database installation you want to perform, and click Next.

Single instance database installation: This option installs the database and the
listener.

Oracle Real Application Clusters database installation: This option installs Oracle
Real Application Clusters.

Oracle RAC One Node database installation: This option installs the Oracle RAC
One Node database.

Screen5: Select Install type:-

Select one of the following, and click Next:

Typical Install: This installation method is selected by default. It lets you quickly
install Oracle Database using minimal input. It installs the software and optionally
creates a general-purpose database using the information that you specify on
this screen.

Advanced Install: This installation method enables you to perform more complex
installations, such as creating individual passwords for different accounts,
creating specific types of starter databases (for example, for transaction
processing or data warehouse systems), using different language groups,
specifying email notifications, and so on.

Screen6: Select Product Languages:-

This option enables you to select the language in which you want to run the product.

Select the product language from the Available Languages list, and move it to the
Selected Languages list. Click Next.
Screen7: Select Database Edition:-

Select Enterprise Edition, Standard Edition, Standard Edition One, or Standard Edition 2.
Click Next.

See Also: "Enabling and Disabling Database Options" for information about enabling
and disabling components that are installed with Oracle Database.

"Product-Specific Postinstallation Tasks" for information about configuring components

that are installed with Oracle Database.

Screen8: Specify Installation Location:-

The Oracle base path appears by default. You can change this path based on your
requirement. Specify Oracle Base, Software Location, and click Next.

The Oracle base directory is a top-level directory for Oracle software installations owned
by an Oracle installation owner account. The default Oracle base path
is mountpoint/app/user, where user is the user account running the installation. You can
change the path based on your requirements.

In the Software Location field, accept the default value or enter the Oracle home
directory path in which you want to install the Oracle software.The directory path must
not contain spaces. Click Next.

Note: This screen is available only with Advanced Installation.

Ensure that the Oracle home path for the database home and the Oracle base path use
only ASCII characters. At the time of this release, the use of non-ASCII characters for an
Oracle database home or Oracle base is not supported.

Screen9: Create Inventory:-

This screen is displayed if this is the first time you are installing Oracle software on your
system.

You are prompted by Oracle Universal Installer to specify the Inventory Directory path
for the central inventory the first time you install any Oracle software on your computer.

Select the oraInventory Group Name of the operating system group that will own the
Oracle Inventory directory (the Oracle Inventory group).

Click Next.

Note: By default, the Oracle Inventory directory is not installed under the Oracle Base
directory. This is because all Oracle software installations share a common Oracle
Inventory, so there is only one Oracle Inventory for all users, whereas there is a
separate Oracle Base directory for each user.

Screen10: Select Configuration Type:-

Select one of the following, and click Next:

General Purpose / Transaction Processing: This is a starter database designed for

general usage or transaction-heavy applications.

Data Warehousing: A starter database optimized to run Data Warehousing

applications.

Screen11: Specify Database Identifiers:-

Provide the following information, and click Next:

Database Naming

Provide the Global Database Name using the following syntax:

db_unique_name.db_domain

db_unique_name is the name of the database. It can contain a maximum of 30

characters if the first 8 characters are unique and begin with an alphabetic
character. The characters can include alphanumeric, underscore (_), dollar sign
($), and pound sign (#), no other special characters are permitted in a database
name.

db_domain is the computer environment used for the database. It can contain no
more than 128 characters (alphanumeric, underscore (_), and pound sign (#)),
inclusive of all periods.

Screen12: Specify Configuration Options:-

Provide the following configuration information, and click Next:

Memory:

Select the Enable Automatic Memory Management option to allow the database to
automatically distribute memory between SGA and PGA. If you do not select this option,
then the SGA and PGA must be sized manually.

See Also: "Consider Memory Allocation and Automatic Memory Management"

Character Sets:

This option enables you to store the character data in the database in one of the
following methods:

Use the default: This option uses the operating system language settings.

Use Unicode: This option enables you to store multiple language groups
 Choose from the following list of character sets: This option enables the Select
Database Character Set drop down list.

Screen13: Specify Database Storage Options:-

Select one of the following options, and click Next.

File System: Specify the database file location.

Oracle Automatic Storage Management.

Screen14: Specify Management Options:-

This screen gives you the option to manage your database using Oracle Enterprise
Manager Cloud Control. Select Register with Enterprise Manager (EM) Cloud
Control and specify the following for Oracle Enterprise Manager Cloud Control
configuration, and click Next:

OMS Host: The system name where the Management repository is running.

OMS Port: The Oracle Enterprise Manager port number to receive requests from
the Management service.

EM Admin Username: The user name to log in to Oracle Enterprise Manager.

EM Admin Password: The password to log in to Oracle Enterprise Manager.

Specify password of ASMSNMP user: The password for the ASMSNMP user
configured in Oracle ASM, required only if you choose Oracle ASM as your
database storage option.

Screen15: Specify Recovery Options:-

Select Enable Recovery to enable recovery using one of the following options:

Select File System to use a file system directory for the fast recovery area, and
then specify the fast recovery area path in the Recovery Area location field.

Select Oracle Automatic Storage Management to use an Automatic Storage

Management disk group for the fast recovery area.

Click Next.

Screen16: Select ASM Disk Group:-

This screen is displayed only if you select Oracle Automatic Storage Management as
your storage option in the Specify Storage Option screen.
Disk groups are created during the Oracle Grid Infrastructure installation. Disk groups
are configured with the SYSASM privilege using asmcmd or SQL create
diskgroup commands. An ASM disk group consists of multiple disk partitions.

The table in this screen displays existing disk groups created during the Oracle Grid
Infrastructure installation. Select the disk group to use for database file storage.

Screen17: Specify Schema Passwords:-

Enter and confirm passwords for the privileged database accounts: SYS, SYSTEM, and
DBSNMP.

If you chose to create the database as a CDB, then Oracle Universal Installer also asks
for the PDBADMIN password.

Click Next.

Screen18: Privileged Operating System Groups:-

The operating system groups are selected by default. You can also manually select
the OSDBA and OSOPER groups.

Select the OSBACKUPDBA, OSDGDBA, and OSKMDBA groups.

Click Next.

Screen19: Perform Prerequisite Checks:-

This option verifies that the minimum system requirements to perform the database
installation are met.

If you click Check Again, then you can run the prerequisite check again to see if the
minimum requirements are met to carry on with the database installation.

Click Fix & Check Again, if you want the installer to fix the problem and verify the
system requirements again.

Note: The Fix & Check Again option generates a script that you must run as
the root user. This generated script sets some system parameters to Oracle-
recommended values. Oracle recommends that you do not modify the contents of this
script.

See Also: "Using Installation Fixup Scripts" for more information.

To get a list of failed requirements, select ShowFailed from the list. To get a list of all
the prerequirement checks run by Oracle Universal Installer, select Show All. To get a
list of the prerequirement checks that are successful, select Show Succeeded.
Note: Oracle recommends that you use caution when selecting the Ignore All option. If
you select this option, then Oracle Universal Installer may not confirm that your system
can install Oracle Database successfully.

Screen20: Summary:-

Review the information displayed on this screen, and click Install.

Note: You can save all the installation steps into a response file by clicking Save
Response File. Later, this file can be used for a silent installation.

Screen21: Install Product:-

This screen displays the progress of a database installation. During this process, the
Execute Configuration Scripts window appears. Do not click OK until you run
the root.sh and, if required, the orainstRoot.sh configuration scripts mentioned in this
screen as the root user. Click Next.

This screen then displays the status information for the configuration assistants that
configure the software and create a database.

A message is displayed at the end of the Database Configuration Assistant process.

Review the database information, specially the Oracle Enterprise Manager Database
Express URL, and click OK.

Note: If this is the first time you are installing Oracle software on your system,
then Oracle Universal Installer prompts you to run the orainstRoot.sh script

Creating RCU for OBIEE 11.1.1.9.0

From the OBIEE Media package, goto rcu home/bin and run the rcu.sh
file

# rcu_home/bin ./rcu.sh

-Click next on welcome screen

-Select Create(to create rcu schema)

-Give the database details

>Database type:**Select Oracle database

>Hostname:**Database host name

>Port:**Database port number

 >Service Name:**database SID

>Username:**User with DBA or sysdba privileges example sys

>Password:**User password

>Role:**sysdba

Clik on Next..

-Create a new prefix for the Schema and select the component as
shown below:

Select Metadata and business Intelligence platform

-Enter password for the Schemas and click next..

-Click on next for the tablespaces to get created by default

-Click on Create

Installing OBIEE 11.1.1.9.0

 -To start the OBIEE installation unzip all five of the OBIEE zip files to a
temporary directory:
-Then from the bishipship/Disk1 subdirectory run:
# ./runInstaller
-Skip the Welcome screen
-Skip the Sotware update
-Select Enterprise installation
-Let the prerequisites checks run
-Create new BI system
Give Username(Example Weblogic)
Enter and confirm password
Click next

-Specify a directory for the Middleware home. The other fields will auto-fill
with default values
>Oracle Middleware home(Give the path where you want to create
middleware home)
>Oracle Home Directory:**BI home path(Auto-fills)
>Weblogic server directory:**wlserver home directory(auto-fills)
>Domain home Location:**domain home(auto-fills)
>Oracle Instance Location:**Instance1 directory path(auto-fills)
>Oracle Instance name: (auto-fills)
-Select all the four components(mandatory part for OBIA configuration)
-Give the details of the BIPLATFORM schema we created in our previous step
Database type:**Oracle
Connect string :*Host:port:sid
BIPlatform username:**prefix_BIPLATFORM
BIPLATFORM Schema password
-Give the details of the MDS schema we created in our previous step
Database type:**Oracle
Connect string :*Host:port:sid
BIPlatform username:**prefix_MDS
BIPLATFORM Schema password
-Select Auto-port configuration
-Skip security updates
-Click on install
-Once the installation is complete,save the summary details file

Check weblogic version which got installet with obiee

 If the weblogic server is 10.3.5, ugrade to weblogic 10.3.6 by applying
patch: 13529623

Before applying the patch, make sure you stop all the services and the node
manager.

Installing Oracle data Integrator

From the OBIA media pack, unzip the ODI files and run the
installer using the command below by invoking java
# ./runInstaller jreLoc <java_path>

For selecting the installation type, make sure to select the below
components
 >Let the prerequisites check run
>Specify Installation location : You must choose the Middleware home
where OBIEE is installed.
>Select weblogic as application server
>In the repository configuration screen, Select skip configuration option as
ODI will be configured later with OBIA configuration.
>Click on Install and wait until installation completes.

Creating RCU for OBIA

>Before running RCU, we need to copy the the dmp files to a new
directory

obia_comp.dmp BI Apps repository

 obia.dmp Data warehouse

obia_odi.dmp ODI Repository

>From the rcu/bin directory run ./rcu

>Use the same credentials used to create OBIEE rcu schema to

create OBIA schema

>Select all the component showing under oracle business

intelligence application

Prefix_DW

Prefix_BIACOMP

Prefix_ODIREPO

>Give the schema password

>in the Custom Variable screen, for the value column, give the
path of the directory in which we had copied the dmp files

>In map tablespace screen, Click on manage tablespaces and

chenage the values of the below

BIAPPS_DW_DATA size- 20GB,Max size-Unlimited

BIAPPS_DW_IDX Size- 5GB,Max size-Unlimited

BIAPPS_DW_STG Size- 10GB,Max size-Unlimited

BIAPPS_DW_TMP-Size- 15GB,Max size-Unlimited

>Click OK >Click on Create

Installing OBIA 11.1.1.10.1

>Unzip the downloaded media pack into a temporary directory
go to the biappsshiphome directory and run:

./runInstaller -jreLoc <OBIEE_HOME>/Oracle_BI1/jdk

>Specify installation location: ** Here,change the bi home

directory to Oracle_BI1
 >Click on Install, Once the installation is done,click on Finish.

Applying Fusion middleware platform patches:

Before beginning ensure OBIEE, ODI and Weblogic is stopped including the
node manager.

There are a number of patches to various Fusion Middleware components that

need to be applied before we can proceed. These patches are all supplied as
part of the BI Apps media pack within three zip files.

Your temporary patch directory should contain 5 sub-directories,

biappsshiphome, odi, oracle_common, soa & weblogic

These directories contain more zip files these will be unzipped by the
script that performs the patch installation.

Now the patch script can be run. This uses perl and needs to be run
from a command window

Change directory to the <OBIEE_HOME>Oracle_BI1biappstoolsbin

directory.

The APPLY_PATCHES.pl script uses a parameter file,

apply_patches_import.txt, to control its process and this is located
in the same directory.

You need to edit this file in a text editor and amend all of the paths
specified. The original file looks like this:
 Once the apply_patches_import.txt file is edited, run the following
command to apply the patch

# perl APPLY_PATCHES.pl <PARAM_INPUT_FILE_PATH>

You can check the log of the patch, present in the WORKDIR
directory

Updating ATG Lite and FSM

>ATG Update, Use the below command using the suitable changes

/u01/app/biapps/Oracle_BI1/jdk/bin/java -jar biappsrepositoryutil.jar

upgradeATG bi.oracle.home=/u01/app/biapps/Oracle_BI1 work.dir=/home/oracle/temp
biacomp.user=BIAPPS_BIACOMP biacomp.password=welcome1
db.conn.sid.url=dbserver:1521:ora12c
atg.db.seed.url=dbserver:1521/ora12c.local.com db.sys.user=sys
db.sys.password=welcome1

> FSM Update, Use the below command using the suitable changes

/u01/app/biapps/Oracle_BI1/jdk/bin/java -jar biappsrepositoryutil.jar upgradeFSM

bi.oracle.home=/u01/app/biapps/Oracle_BI1 work.dir=/home/oracle/temp
biacomp.user=BIAPPS_BIACOMP biacomp.password=welcome1 db.conn.sid.url=
dbserver:1521:ora12c fsm.db.seed.url=dbserver:1521/ora12c.local.com
db.sys.user=sys db.sys.password=welcome1
 Configure BI Application

At this point the BI Apps and ODI software has been installed but not yet
deployed to the weblogic server. So the next step is run the configuration
wizard to perform the deployments.

In summary the following components are about to be deployed:

Oracle BI Applications Configuration Manager

Functional Setup Manager

ODI

Java EE Agent

ODI Console

Load Plan Generator

Also an Administrator user for BI Apps will be created and the ODI repository
will be configured.

To start the configuration wizard locate and run the following command:

<OBIEE_HOME>/Oracle_BI1/bin/configApps.sh

> Skip past the welcome screen:

> Confirm the prerequisite checks pass ok:

> Enter the password for the Weblogic admin user (the other fields should be
default filled):

> The next screen shows you the home location details, but you cant change
anything

> Select BI Application Components to install:

> You now need to specify a password for the OBIEE repository a new RPD
file will be installed by this process.
> Now you need to provide the location and user-id/password for the OBIEE
MDS schema created by the RCU when OBIEE was installed.

> Next comes the BI Apps repository schema BIAPPS_BIACOMP, created by

the BI Apps RCU:

> Then it needs the connection details for the data warehouse schema,
BIAPPS_DW:

> And finally the ODI Repository schema, BIAPPS_ODI_REPO:

> Next you can specify the ports, but again Im keeping defaults 9704 for
BIACM and 15001 for the ODI Console:

> Then confirm the details are correct before starting the configuration:

> Let the configuration progress

> Take a note of the installation details (URLs etc) and save them before
closing the Configuration tool.