9/13

4 Prerequisites

Before installation, make sure that the database instance and tablespace are already created.

1. Install Oracle Database 11g Release 2 (11.2.0.4) instance with a Database Administrator's guidance.

2. Create the HDWF database instance and the location of the data file. Note down the service name and verify the existence of the data file location.

3. Create a temporary tablespace for the HDWF schema and the HDWF Interface schema based on your requirements. If suitable, you can also use the default temp tablespace instead of creating a new one.

4. Use only lowercase folder names in all platforms that are to be created and used by the installer.

5. To create an encrypted tablespace during fresh installation of HDWF 6.1, there are certain prerequisite steps to be followed. For information on setting up your environment for tablespace encryption, see Oracle Database documentation.

6. If you are installing HDWF 6.1 on a Exadata database machine, see the following sections to familiarize yourself with Exadata documentation:

   • Chapter 5

   • Exadata Machine in the Oracle® Healthcare Data Warehouse Foundation Programmer's Guide.

   • Exadata Implementation in the Oracle® Healthcare Data Warehouse Foundation Interface Tables Programmer's Guide.

7. If you are upgrading HDWF 6.0 to 6.1, see Section 5.5, if applicable, for data migration details.

   When running the HDWF installer, ensure that:

   • The parameters specified to connect to the required database are accurate. You can verify this using the following command:

     SQL>connect <username>@"(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=<hostname>)(PORT=<port number>))(CONNECT_DATA=(SERVICE_ NAME=<service_name>)))"

     Enter the password when prompted.

     Substitute the variables (<variable_name>) with the actual values you have provided during installation using the Oracle Universal Installer (OUI).

     If the above command does not generate a connection to the required database, check the parameters you have provided.

   • There are no trailing and leading spaces when entering parameters in the installer.

   • If you are rerunning the initial install script after a failure, check that you have deleted the tablespace and (or) users that were created as part of the previous unsuccessful installation.

   • Take a backup of both interface tables schema and HDM schema before upgrading from HDWF 6.0.

   • In a fresh installation, check that the data file path provided while creating the tablespace is correct. OUI does not check the path existence.

   • Table compression strategy is decided based on the number of updates in HDWF tables. If the number of updates is high (as a result of versioning in HDWF tables), select the OLTP compression instead of HCC (QUERY HIGH).

   • For a fresh installation of HDWF 6.1 on an Exadata environment, selecting the compression type as HCC (QUERY HIGH) will slow down the first few incremental loads.

   • If the installation fails, view the generated log files. For details on the log files, see Section 5.2.

8. Ensure that you have set the NLS_LENGTH_SEMANTICS parameter to either CHAR or BYTE, based on your requirements.

   For HDWF Globalization Support information, see Oracle® Database Globalization Support Guide and set your database character set accordingly.

9. Since the installer script is executed in the SH shell of Linux or Unix, convert the installer execution shell to SH shell.

10. Copy the oraInst.loc file from <ORACLE_HOME> to the installation directory. Create a new directory named inventory in the installation directory. Update oraInst.loc to reflect the path of this newly created inventory directory.

    Enter the following details in oraInst.loc:

    inventory_loc=< HDWF_HOME >/inventory

    inst_group=dba

Note:

If oraInst.loc file is not found in ORACLE_HOME, create a new file named oraInst.loc.