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:
Parent topic: Data Model 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:
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:
|
|
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. |
Parent topic: Install the Data Model without Pre-created User Schemas
Prepare the Installer
- | Steps |
---|---|
The Oracle Healthcare Foundation 8.2.0.0.0 software
is available for download from the Oracle Software Delivery Cloud ( |
|
Extract the contents of the Oracle Healthcare Foundation media pack to your system. |
|
Open the media_pack_location/ folder. |
|
Unzip the
|
|
Open the Disk1/install folder. |
|
Change the protection on the files as follows: chmod 755 * |
Parent topic: Install the Data Model without Pre-created User Schemas
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.0.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:
|
|
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 if it is licensed. |
|
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:
|
|
Summary |
Click Install. |
|
End of Installation |
Click Exit after reviewing the installation information. At the confirmation prompt, click Yes to exit the installer. |
Parent topic: Install the Data Model without Pre-created User Schemas
Check the Installation
- | Steps |
---|---|
Review the generated installation log files for errors. For details, see
|
|
Contact Oracle support, if necessary, to resolve any errors. |
Parent topic: Install the Data Model without Pre-created User Schemas