2 Prerequisites

This chapter contains the following topics:

Section 2.1, "Prerequisites for the Installation"
Section 2.2, "General Guidelines for the Installer"
Section 2.3, "Preinstallation Steps for Upgrading from OHADI 3.0 to 3.1"
Section 2.4, "Installation Log Files"

2.1 Prerequisites for the Installation

Before you can install the OHADI application, complete the following pre-installation tasks:

You should have good knowledge of Oracle Database, Oracle Data Integrator (ODI), and Linux OS.
For 11g installation, install Oracle Database 11.2.0.4 (11g) and Oracle Data Integrator 11.1.1.7.0.
Install Oracle Healthcare Data Warehouse Foundation 6.1. Follow the instructions in Oracle Healthcare Data Warehouse Foundation Patch Readme and Release Notes.
Make sure that Temporary tablespace (Temp) is available for DB schema creation through installer.
Make sure that Temporary Tablespace (Temp) is available in the DB where the Metadata Configuration schema (for HDWF DB) and Repository schemas (Repository DB) are created. If it is not available, make sure that it is created manually before starting the installer.
Create a separate Permanent Tablespace or provide existing Permanent Tablespace for ODI repository DB schema creation. The installer does not create any table spaces.
At least 2 GB space should be available in the installation directory.
For remote installation (that is, if the ODI repository DB is present in the remote server, and you are installing on a Linux or Unix machine), make sure the following are met:
- Mount the (datapump) directory of the remote DB server to the installation server with appropriate read and write privileges.
- Make sure that the remote directories are accessible after mounting from the installation server.
- The Linux user of the remote server, who executes the Oracle process, must have the privilege of 777 to the directory (datapump).
- If the repository DB exists on an Exadata machine, repository DB single node (the node which is being mounted) should be provided in input screen for ODI DB host server.
Make sure that the System, HDWF, or Interface schema users do not display the expiry notification upon logging into the database. If an expiry notification is displayed, reset your password before running the installer.

Note:

In the following sections, the text enclosed within <> indicate parameters. You need to provide the parameter values as per your system.

2.2 General Guidelines for the Installer

This installer is for a fresh or upgrade installation of the OHADI or HLI (Health Language, Inc.) product.
The installation scripts are coded in Linux OS. Make sure the installation server is compatible.
As the installer is 64-bit, your installation server should also be a 64-bit OS.
The Linux X-Windows should be used for the Linux Oracle Universal Installer (OUI) installation (Linux graphical user interface).
Only one installer instance should be executed at a time. Oracle does not recommend running multiple instances of the installer.
The installer exits when the script encounters an error. You must check for errors manually before restarting the installer.
While entering installation details, do not leave any space before or after the input details in the test box.
OUI throws an error on entering an invalid path in the installation server. Do not enter any space before path declaration, after the path configuration, or in between paths.
Installation folder names should not have any spaces.
Do not leave any text box blank in the OUI. The OUI throws an error and does not let you traverse through the OUI screen.
If any install script fails, an installer status email is sent to the configured email address (specified during installation).
The OUI installer can be re-executed multiple times but the installed script is skipped from re-execution.
The OUI installer does not fix any issues automatically. If the installation fails, you must manually verify and fix the issues.
If you click Stop Installation during installation, the OUI installer stops. However, the current script execution (if any), runs in the server, which needs to be stopped manually.
The OUI installer does not validate the system space requirement of the installation server. Make sure that there is enough space in the installation directory and Oracle home directory.
The installer must run on the system where ODI is installed.
When you are re-executing the installer due to a failure, enter the same details in the question prompting phase at all times. Do not delete any objects in the installation folder.
For re-installing the code on a different server path, rename all the files in $ORACLE_BASE/oraInventory/ContentsXML/ directory, before executing the installer.

2.3 Preinstallation Steps for Upgrading from OHADI 3.0 to 3.1

Interface tables must not be loaded during installation or data migration process.
Make sure that existing interface data is processed to HDM (using OHADI 3.0).
Complete the ETL execution cycle.

2.4 Installation Log Files

During installation, the OUI generates the following log files:
- installActions<timestamp>.log - This log file records the action of the installer and helps in diagnosing problems with the installation.
- oraInstall<timestamp>.out - This output file records all the output of SQL scripts that are run by the installer.
- oraInstall<timestamp>.err - This error file records all the errors from the scripts run by the installer. You must include the above log files while reporting any problems that occur during installation. The log files are time stamped and each installation session creates a new log file.
  
  On a Linux installation, the log files are located at $ORACLE_BASE/oraInventory/logs.
  
  For example, /u01/app/oraInventory/logs
In the back end, the installer creates the following directories:

For OHADI:
- ohadi_xmls -- OHADI repository data
- ohadi_sql -- OHADI DB configuration scripts
- ohadi_scripts -- OHADI installation scripts
- ohadi_logs -- OHADI installation logs
For HLI:
- hli_xmls -- HLI repository data
- hli_sql -- HLI DB configuration scripts
- hli_scripts -- HLI installation scripts
- hli_logs -- HLI installation logs
These directories are created under the path:

OHADI path: <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.ohadi/

HLI path: <OHADI_INSTALL_DIR>/ohadi_oui/oracle.hsgbu.hli/
OHADI installation consists of multiple steps. The execution status of each file is captured in a summary log.

The following is an example:

OHADI

OHADI_ODI_DATABASE_SETUP - OHADI data model and seed data setup

OHADI_ODI_MASTER_WORK_CREATE - OHADI ODI master and work repository user creation

OHADI_ODI_DATADUMP_CREATE - OHADI ODI XML data directory updation

OHADI_ODI_MASTER_IMPORT - OHADI ETL dump import

OHADI_ODI_WORK_REP_UPDATE - OHADI work repository updation

OHADI_SCHEMA_ENC_PASWD - OHADI ODI schema password encryption

OHADI_ODI_UTIL_FILE_CREATE - OHADI ODI Utility file creation

OHADI_ODI_REPO_TOPOLOGY_UPDATE - OHADI relation connection updation in repository

OHADI_ODI_INSTALL_VERIFICATION - OHADI few ETL test for validation

HLI

HLI_ODI_DATABASE_SETUP - HLI data model and seed data setup

HLI_ODI_MASTER_WORK_CREATE - HLI ODI master and work repository user creation

HLI_ODI_MASTER_IMPORT - HLI ETL dump import

HLI_ODI_WORK_REP_UPDATE - HLI work repository updation

HLI_SCHEMA_ENC_PASWD - HLI ODI schema password encryption

HLI_ODI_UTIL_FILE_CREATE - HLI ODI Utility file creation

HLI_ODI_REPO_TOPOLOGY_UPDATE - HLI relation connection updation in repository

HLI_ODI_INSTALL_VERIFICATION - HLI few ETL test for validation

Each of the above steps may consist of separate log file indicating the other steps involved and their execution status.

For example:

OHADI_ODI_DATABASE_SETUP_SUMMARY.log will have all data model and seed data related execution status.

You should include the OUI generated log files and OHADI specific log files while reporting any problems that occur during installation.