2 Prerequisites

Oracle expects that you have good knowledge of concepts and commands of Linux operating system, ODI, and Oracle DB.

Before installing the OHADI Application Toolkit, you must complete the following pre-installation tasks:

For 11g installation, install Oracle DB 11.2.0.4 and ODI 11.1.1.7.0. Follow the instructions in Oracle Database Installation Guide for Linux and Oracle Data Integrator Guide.
Install Oracle HDWF 6.1. Follow the instructions in Oracle Healthcare Data Warehouse Foundation Patch Readme and Oracle Healthcare Data Warehouse Foundation Patch Release Notes.
Check the COMPATIBLE parameter for your database using the following command:

show parameter COMPATIBLE

For example, for 11g database, the COMPATIBLE parameter must be of 11g.
Ensure that the database instance is already created.
The installer prompts for the data mart data file location. You can either create location for the Application Toolkit data mart data file or verify the existence of the data file location. Oracle recommends you to use the path of existing table space directory where all .dbf files exist.
Create a temporary tablespace for the Application Toolkit data mart schema or use the default temp tablespace based on your needs.
Install all schemas on a single database instance.
Use only lowercase for all folder names in all platforms to be created and used by the installer. Installation folder names must not have any spaces.
If the repository database is present in a remote server and you are installing from the Linux OS, mount the datapump (dpdump) directory of the remote database server to the installation server with appropriate read and write privileges. The Linux user of the remote server executing the Oracle process must have minimum privilege of 444 (read access to any users) to the files (logs), which are created by the IMPDP command.
If the repository database exists in the Exadata machine, you must add the repository database single node (the node which is mounted) TNS entry in the tnsnames.ora file in the installation server.
After installation, you must revert the TNS entry to multi-node.
Ensure the database TNS entry for HDWF database or repository database has connection string, which is same as SID of the respective database.
Ensure that the System, HDWF, and HCD schema users do not display the Password expiry notification when you log in to the database.
Create a ContentsXML_backup directory in the <ORACLE_ BASE>/oraInventory/ContentsXML/ directory. Move all files in this directory to the backup directory created before executing the installer.
Ensure the DB used in the installation has the corresponding TNS entry in the tnsnames.ora file (on the installation server). This is applicable if you are performing the remote installation.
Installation server must be of 64 -bit OS.
The database connection parameters such as host name, database port number, and service name to be specified in the installer are correct. You can verify it by executing the connect command on SQL*Plus using these parameters on the machine, where you are running the installer and connecting to the target database.
There are no trailing and leading spaces when entering parameters in the installer.
If you are running the initial install script after it failed the first time, ensure that you have deleted the HCD tablespace and/or users that are created as a part of the previous unsuccessful installation.
Ensure that the path of the data file mentioned while creating the tablespace is correct. The OHADI Application Toolkit installer does not check the path.
If the installation fails, view the generated log files. For details about log files, see Section 3.2.
Oracle Universal Installer (OUI) displays an error on entering an invalid password for the database user name, such as system. When prompted, enter a valid password.
OUI installer can be re-executed multiple times but the installed script is skipped from re-execution.
OUI installer does not fix any issues automatically. If the installation fails, you must manually verify and fix the issues.
When re-executing the installer due to a failure, enter the same details in the question prompting phase at all times what you entered previously. Upon restarting, you must not change any parameter that you had entered. Do not delete any files in the installation folder.
Clicking Stop Installation during installation stops the OUI installer. However, the current script execution (if any), runs in the server and must be stopped manually.
Only one installer instance must be executed at a time. Oracle does not recommend running multiple instances of the installer.
The installer must run on the system where ODI is installed.
The OUI installer does not validate the system space requirement of the installation server. Ensure that there is enough space in the installation directory and Oracle Home directory.