This chapter describes how to install the OHF Data Model. There are two ways to install the Data Model, depending on how you create the user schemas. The installer can create the user schemas during the installation or you can create them manually, prior to the installation:
This section describes how to install the Data Model by using the installer to create fresh user schemas.
Install Oracle Database 12.2.0.1 Enterprise Edition. | |
Make sure that the database compatible parameter is set to 12.2.0.1.0 by connecting to the DBA user and running the query below:
select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.2.0.1.0, ask your database administrator to set it. |
|
If you are installing OHF on an Exadata environment, apply the Oracle database patch 19562381 (Doc ID >19562381.8). | |
Create a container database with a single pluggable database instance with the help of a Database Administrator. | |
Make sure the database initialization parameter MAX_STRING_SIZE is set to STANDARD (default value). | |
Install Java Virtual Machine on the database server. | |
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. |
|
Enable database connection through SERVICE_NAME. Make sure that you are connecting to the pluggable database instance.
Verify the database connectivity using the following command: SQL>connect <username>@<hostname>:<port number>/<service name> or sqlplus <username>@'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<dbhost>)(PORT=<dbport>))(CONNECT_DATA=(SERVICE_NAME=<dbservicename>)))' |
|
Make sure that the Sqlplus utility is available in the installation server. | |
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, etc. The installer only checks whether the keystore is open if the sys and system passwords are provided during the installation. | |
Set the GLOBAL_NAMES database initialization parameter to false. | |
For remote installations, make sure the following are available on the client machine:
|
|
If you are installing OHF on an Exadata database machine, see the Exadata Machine and Exadata Implementation sections in the Oracle Healthcare Foundation Programmer's Guide. | |
Table compression strategy is decided based on the number of updates in tables. If the number of updates is high, select the Advanced compression option instead of HCC (QUERY HIGH). | |
If you are installing OHF on an Exadata environment, selecting the compression type as HCC (QUERY HIGH) will slow down the first few incremental loads. | |
Make sure that you have an appropriate database license for the compression methods you choose. | |
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. |
Extract the contents of the OHF media pack to your system. | |
Open the <media_pack_location>/ folder. | |
Unzip the OHF_721_Linux-x64.zip file where you want to launch the installer using the following command:
|
|
Open the Disk1/install folder. | |
Change the protection on files as follows:
|
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 7.2.1.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 12.2.0.1.0) client home path. | |
Database Configuration | Enter values for the following fields:
|
|
Table Compression | On an Exadata setup, use the following compression options:
Interface Tables schema
Data Warehouse schema
Common Data Mart schema
Cohort Data Mart schema
Omics Data Bank schema
On a non-Exadata setup, for each of the above schemas, choose either No Compression (default) or Advanced Compression. |
|
Data Model Configuration | Enter values for the following fields:
|
|
Data Model Configuration | Enter values for the following fields:
|
|
Data Model Configuration | Enter values for the following fields:
|
|
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: ASM: Note:
|
|
Tablespace Details | The installer creates the following tablespaces. Make sure that these tablespaces do not exist in the database.
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.
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:
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. |
Review the generated installation log files for errors. For details, see Installation Log Files. | |
Contact Oracle support, if necessary, to resolve any errors. |
This section describes how to install the Data Model by creating OHF user schemas and tablespaces outside the installer, then using the installer to create database objects in the respective user schemas.
Install Oracle Database 12.2.0.1 Enterprise Edition. | |
Make sure that the database compatible parameter is set to 12.2.0.1.0 by connecting to the DBA user and running the query below:
select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.2.0.1.0, ask your database administrator to set it. |
|
If you are installing OHF on an Exadata environment, apply the Oracle database patch 19562381 (Doc ID >19562381.8). | |
Create a container database with a single pluggable database instance with the help of a Database Administrator. | |
Make sure the database initialization parameter MAX_STRING_SIZE is set to STANDARD (default value). | |
Install Java Virtual Machine on the database server. | |
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. |
|
Enable database connection through SERVICE_NAME. Make sure that you are connecting to the pluggable database instance.
Verify the database connectivity using the following command: SQL>connect <username>@<hostname>:<port number>/<service name> or sqlplus <username>@'(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<dbhost>)(PORT=<dbport>))(CONNECT_DATA=(SERVICE_NAME=<dbservicename>)))' |
|
Make sure that the Sqlplus utility is available in the installation server. | |
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, etc. The installer only checks whether the keystore is open if the sys and system passwords are provided during the installation. | |
Set the GLOBAL_NAMES database initialization parameter to false. | |
For remote installations, make sure the following are available on the client machine:
|
|
If you are installing OHF on an Exadata database machine, see the Exadata Machine and Exadata Implementation sections in the Oracle Healthcare Foundation Programmer's Guide. | |
Table compression strategy is decided based on the number of updates in tables. If the number of updates is high, select the Advanced compression option instead of HCC (QUERY HIGH). | |
If you are installing OHF on an Exadata environment, selecting the compression type as HCC (QUERY HIGH) will slow down the first few incremental loads. | |
Make sure that you have an appropriate database license for the compression methods you choose. |
Create the following default tablespaces. You can use different tablespace names than the ones listed below.
Tablespace Name | Big File Tablespace | Description | |
---|---|---|---|
hdi_ts | Yes | Default tablespace for the Interface Tables (hdi) schema | |
hdm_ts | Yes | Default tablespace for the Data Warehouse (hdm) schema | |
hcd_ts | Yes | Default tablespace for the Common Data Mart (hcd) schema | |
odb_data_ts | Yes | Default tablespace for the Omics Data Bank (odb) schema | |
odb_index_ts | Yes | Used for indexes of the Omics Data Bank (odb) schema | |
odb_lob_ts | Yes | Used for LOB columns in the Omics Data Bank (odb) schema | |
cdm_data_ts | Yes | Default tablespace for the Cohort Data Mart (cdm) schema | |
cdm_index_ts | Yes | Used for indexes of the Cohort Data Mart (cdm) schema | |
ent_ts | No | Default tablespace for the Enterprise (ent) schema | |
job_data_ts | No | Default tablespace for the Job Engine (job) schema | |
job_index_ts | No | Used for indexes of the Job Engine (job) schema | |
job_store_ts | No | Database File System (DBFS) store created as part of the Job Engine installation | |
job_lob_ts | No | Name of the tablespace to store LOB data in the DBFS store created for the JOB ENGINE schema user | |
job_tbs_ts | No | Name of the tablespace to be used for the DBFS store created for the JOB_ENGINE schema | |
svc_ts | No | Default tablespace used for the Services (svc) schema | |
api_ts | No | Default tablespace for the Clinical Genomics (cga) API schema. |
Create the following temporary tablespaces. You can use different tablespace names than the ones listed below.
Tablespace Name | Big File Tablespace | Description | |
---|---|---|---|
hdi_temp | Yes | Temporary tablespace for the Interface Tables (hdi) schema | |
hdm_temp | Yes | Temporary tablespace for the Data Warehouse (hdm) schema | |
hcd_temp | Yes | Temporary tablespace for the Common Data Mart (hcd) schema | |
odb_temp | Yes | Temporary tablespace for the Omics Data Bank (odb) schema | |
cdm_temp | Yes | Temporary tablespace for the Cohort Data Mart (cdm) schema | |
ent_temp | No | Temporary tablespace for the Enterprise (ent) schema | |
job_temp | No | Temporary tablespace for the Job Engine (job) schema | |
svc_temp | No | Temporary tablespace for the Services (svc) schema | |
api_temp | Yes | Temporary tablespace for the Clinical Genomics (cga) API schema |
Extract the contents of the OHF media pack to your system. | |
Open the <media_pack_location>/ folder. | |
Unzip the OHF_721_Linux-x64.zip file where you want to launch the installer using the following command:
|
Navigate to the directory <media_pack_location>/Disk1/stage/Components/oracle.hsgbu.hc.datamodel/7.2.1.0.0/1/DataFiles/Expanded/filegroup1. | |
Unzip the master_install.zip file. | |
Connect to Oracle SYS from the extracted content and create database roles by executing the roles.sql script. |
Create the following user schemas and assign the appropriate default and temporary tablespaces. Refer to Create Default Tablespaces and Create Temporary Tablespaces for details. If you created tablespaces with different names, use those names instead.
Schema | Default Tablespace | Temporary Tablespace | |
---|---|---|---|
Interface Tables (hdi) | hdi_ts | hdi_temp | |
Data Warehouse (hdm) | hdm_ts | hdm_temp | |
Common Data Mart (hcd) | hcd_ts | hcd_temp | |
Omics Data Bank (odb) | odb_data_ts | odb_temp | |
Cohort Data Mart (cdm) | cdm_data_ts | cdm_temp | |
Enterprise (ent) | ent_ts | ent_temp | |
Job Engine (job) | job_data_ts | job_temp | |
Services (svc) | svc_ts | svc_temp | |
Clinical Genomics (cga) | api_ts | api_temp |
Execute the following scripts/commands as a DBA user. When prompted, enter the respective schema names.
When prompted for the application role, enter OHF_APPLICATION_ROLE.
@hdi_install/grant_schema_priv.sql |
|
@hdm_install/grant_schema_priv.sql |
|
@hcd_install/grant_schema_priv.sql |
|
@odb_install/grant_schema_priv.sql
Execute the following commands: > > |
|
@cdm_install/grant_schema_priv.sql
Execute the following command: > |
|
@enterprise_install/grant_schema_priv.sql |
|
@job_install/grant_schema_priv.sql
Execute the following commands:
|
|
@svc_install/grant_schema_priv.sql |
Make sure that all the OHF schemas are disconnected from the database by querying gv_$session from the sys user:
select * from sys.gv_$session where status <> 'KILLED' and username in ('<OHF Schemas>'); |
|
Navigate to the <media_pack_location>/Disk1/install folder. | |
Change the protection on files as follows:
|
|
Start the Oracle Universal Installer (OUI) using the following command:
The The |
Screen | Action | |
---|---|---|
Welcome | Click Next. | |
Select a Product to Install | Select the Oracle Healthcare Foundation Data Model 7.2.1.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 12.2.0.1.0) client home path. The installer validates this path. | |
Database Configuration | Enter values for the following fields:
The installer will not validate the database connectivity. Make sure that you are able to connect to the database from SQLPlus. |
|
Table Compression | On an Exadata setup, use the following compression options:
Interface Tables schema
Data Warehouse schema
Common Data Mart schema
Cohort Data Mart schema
Omics Data Bank schema
On a non-Exadata setup, for each of the above schemas, choose either No Compression (default) or Advanced Compression. |
|
Data Model Configuration | Enter values for the pre-created schemas:
|
|
Data Model Configuration | Enter values for the pre-created schemas:
|
|
Data Model Configuration | Enter values for the following fields:
|
|
Data Model Configuration Verification | Click Next. | |
Tablespace Details | Click Next. | |
Temporary Tablespace Details | Click Next. | |
Omics Data Bank and Cohort Data Mart Parameters | Enter values for the following fields:
Execute the following query to find all store names in the database (created by all previous installations) by connecting to the SYS user:
Note: If you have store names in the database that do not match the
|
|
Tablespace Parameters | Enter values for the fields below from the existing or pre-created CDM, ODB, and Job engine schemas. Make sure that these tablespaces exist or were created before the installation. Refer to Create Default Tablespaces for the tablespace names to be used.
|
|
Summary | Click Install. | |
End of Installation | Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer. |
Review the generated installation log files for errors. For details, see Installation Log Files. | |
Contact Oracle support, if necessary, to resolve any errors. |
After the Cohort Data Mart (CDM) and Omics Data Bank (ODB) data model installation, connect to the database user with DBA privilege, and execute the following scripts to revoke privileges:
REVOKE CREATE ANY DIRECTORY FROM <odb user>
REVOKE CREATE ANY CONTEXT FROM <cdm user>
where,
<odb_user>
is the ODB schema name.
<cdm_user>
is the CDM schema name.