Install the Data Model without Pre-created User Schemas

This section describes how to install the Data Model by using the installer to create fresh user schemas. Please complete the following:

• Check Prerequisites
  
• Prepare the Installer
  
• Run the Installer
  
• Check the Installation
  

Check Prerequisites

-	Prerequisites
	Install Oracle Database Enterprise Edition 19c (19.3) with the latest patches.
	Make sure that the database compatible parameter is set to 19.3.0.0.0 or higher by connecting to the DBA user and running the query below: select * from v$parameter where name = 'compatible'; Ensure the parameter is set to 19.3.0.0.0 or higher.
	Create a container database with a single pluggable database instance with the help of a Oracle Database Administrator (optional).
	Make sure the database initialization parameter MAX_STRING_SIZE is set to STANDARD (default value). Note that this parameter cannot be changed to STANDARD if the database is created with MAX-STRING_SIZE set to EXTENDED.
	Set the NLS_LENGTH_SEMANTICS parameter to either CHAR or BYTE, based on your requirements. For Oracle Healthcare Foundation Globalization Support information, see Oracle Database Globalization Support Guide and set your database character set accordingly.
	Make sure that the password expiry notification message does not display for the sys and system schemas.
	To create an encrypted tablespace during the installation, set up your environment for tablespace encryption. For more information, see Oracle Database Advanced Security Guide 12.2. The installer only creates the tablespace and does not handle prerequisites like setting up the keystore, opening it, and so forth. The installer only checks whether the keystore is open if the sys and system passwords are provided during the installation.
	Verify if you have a database license for Advanced Compression.
	Set the GLOBAL_NAMES database initialization parameter to false.
	If you are installing Oracle Healthcare Foundation on an Exadata database machine, see the Exadata Machine and Exadata Implementation sections in the Oracle Healthcare Foundation Programmer's Guide.
	For remote installations, make sure the following are available on the client machine: Oracle Linux 6.7 (64-bit) OS or above Oracle Database Enterprise Edition 19c (19.3) with the latest patches and with the Sqlplus utility
	Verify the database connectivity through SERVICE_NAME. Make sure that you are connecting to the pluggable database (PDB) if installing in a container-based environment. Verify the database connectivity using the following command: SQL>connect username@hostname:port number/service name orsqlplususername@'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=dbhost)(PORT=dbport)) (CONNECT_DATA=(SERVICE_NAME=dbservicename)))'
	The installer does not validate the tablespace data files location. If the database server is on the remote server, make sure the location physically exists or the installer will fail.

Prepare the Installer

-	Steps
	The Oracle Healthcare Foundation 8.2.2.0.0 software is available for download from the Oracle Software Delivery Cloud (https://edelivery.oracle.com). Search for Oracle Healthcare Foundation 8.2.2.0.0
	Extract the contents of the Oracle Healthcare Foundation media pack to your system.
	Open the media_pack_location/ folder.
	Unzip the OHF_V821_Linux-x64.zip file where you want to launch the installer using the following command: unzip -a OHF_V821_Linux-x64.zip
	Open the Disk1/install folder.
	Change the protection on the files as follows: chmod 755 *

Run the Installer

Start the Oracle Universal Installer (OUI) using the following command:

• If the database server (Exadata or non-Exadata) is on the machine where the installer is running, execute:

  sh runInstaller.sh -local

• If the database server is on a different machine, execute:

  sh runInstaller.sh -local remote_installation=true

where the -local option is to install on the local node irrespective of the cluster nodes specified on the installer machine.

-	Screen	Action
	Welcome	Click Next.
	Select a Product to Install	Select the Oracle Healthcare Foundation Data Model 8.2.2.0.0 option.
	Specify Home Details	Enter the installation home name and location.
	Verify Installation Prerequisites	Verify if all the prerequisites are met before proceeding.
	Oracle Client Home Configuration	Specify the Oracle (version 19.3.0.0.0) client home path.
	Database Configuration	Enter values for the following fields: Hostname - By default, the system host name appears. For remote installations, set this value to the host name of the remote machine. Port - By default, the port number is 1521. You can edit this field if required. Service name System user password Sys user password
	Table Compression	On an Exadata setup, use the following compression options: Interface Tables schema Hybrid columnar compression (default) No Compression Data Warehouse schema No Compression (default) Advanced Compression: Preferred if updates are high. If you don't have a license for Advanced Compression, select Hybrid Columnar Compression. Hybrid Columnar Compression Common Data Mart schema No Compression (default) Advanced Compression Cohort Data Mart schema No Compression (default) Advanced Compression Omics Data Bank schema Hybrid columnar compression (default) On a non-Exadata setup, for each of the above schemas, choose either No Compression (default) or Advanced Compression if it is licensed.
	Data Model Configuration	Enter values for the following fields: Interface Tables schema name Interface Tables schema password Data Warehouse schema name Data Warehouse schema password Common Data Mart schema name Common Data Mart schema password Omics Data Bank schema name Omics Data Bank schema password
	Data Model Configuration	Enter values for the following fields: Cohort Data Mart schema name Cohort Data Mart password Enterprise schema name Enterprise schema password Job Engine schema name Job Engine schema password Services schema name Services schema password
	Data Model Configuration	Enter values for the following fields: Clinical Genomics (cga) schema name Clinical Genomics (cga) schema password
	Data Model Configuration Verification	Click Next.
	Tablespace Data File Location	Specify the location of the Tablespace data files. This is the directory on the database server where the data files are created during the installation. For example, Unix: /u01/oradata/dbname ASM: +DATA_EX02/hashas01/datafile Note: The ASM location must always start with +. The path should not end with /.
	Tablespace Details	The installer creates the following tablespaces. Make sure that these tablespaces do not exist in the database. hdi_ts - Default tablespace used for Interface tables (hdi) schema hdm_ts - Default tablespace used for Data Warehouse (hdm) schema hcd_ts - Default tablespace used for Common Data Mart (hcd) schema odb_data_ts - Default tablespace used for Omics Data Bank (odb) schema odb_index_ts - Tablespace used for indexes of the Omics Data Bank (odb) schema odb_lob_ts - Tablespace used for LOB columns in the Omics Data Bank (odb) schema cdm_data_ts - Default tablespace used for Cohort Data Mart (cdm) schema cdm_index_ts - Tablespace used for indexes of the Cohort Data Mart (cdm) schema ent_ts - Default tablespace used for Enterprise (ent) schema job_data_ts - Default tablespace for Job Engine (job) schema job_index_ts - Tablespace used for indexes of the Job Engine (job) schema job_store_ts - Database File System (DBFS) store is created as part of the Job Engine installation job_lob_ts - Tablespace used to store LOB data in the DBFS store created for the JOB ENGINE schema user job_tbs_ts - Tablespace used for the DBFS store created for the JOB_ENGINE schema svc_ts - Default tablespace used for services schema (svc) api_ts - Default tablespace used for Clinical Genomics schema (cga) For each schema, you can edit the default tablespace name, initial size, max size, and tablespace encryption.
	Temporary Tablespace Details	The installer creates the following temporary tablespaces. Make sure that these tablespaces do not exist in the database. hdi_temp - Temporary tablespace for the Interface tables schema (hdi) hdm_temp - Temporary tablespace for the Data Warehouse schema (hdm) hcd_temp - Temporary tablespace for the Common Data Mart schema (hcd) odb_temp - Temporary tablespace for the Omics Data Bank schema (odb) cdm_temp - Temporary tablespace for the Cohort Data Mart schema (cdm) ent_temp - Temporary tablespace for the Enterprise schema (ent) job_temp - Temporary tablespace for the Job Engine schema (job) svc_temp - Temporary tablespace for the Services schema (svc) api_temp - Temporary tablespace used for Clinical Genomics schema (cga) For each schema, you can edit the temporary tablespace name, initial size, and max size.
	Omics Data Bank and Cohort Data Mart Parameters	Enter values for the following fields: Result Partition - Used to partition result tables in the ODB schema. The available options are: GENE (Default) Promoter Offset - Numerical value to specify a portion of the gene used as a promoter in the ODB schema. The default value is 200. Flanking Offset - Numerical value to specify the region before and after a gene to link results to a gene in the ODB schema. The default value is 200. Max Parallel Degree - An option to specify the maximum degree of parallelism to be set on tables or used in the SQL statements for the CDM or ODB schema. It is dependent on the machine configuration of the database server. The default value is 2. Job Store Name - If you are using the same database instance for multiple environments, enter a unique job store name for each job schema.
	Summary	Click Install.
	End of Installation	Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer.

Check the Installation

-	Steps
	Review the generated installation log files for errors. For details, see Installation Log Files.
	Contact Oracle support, if necessary, to resolve any errors.