Upgrading from Healthcare Data Warehouse Foundation or a Previous Oracle Healthcare Foundation Version

For the list of supported upgrade paths, see Supported Upgrade Paths.

If you are upgrading from Healthcare Data Warehouse Foundation (HDWF) 6.1 to Oracle Healthcare Foundation, you must install Oracle Healthcare Analytics Data Integration (OHADI) 3.1.

Note:

After upgrading, continue to Data Migration for instructions on how to migrate data from Healthcare Data Warehouse Foundation to Oracle Healthcare Foundation.

To upgrade from HDWF 6.1 to Oracle Healthcare Foundation, upgrade the Healthcare Data Warehouse Foundation 6.1 database instance to Oracle Database 19c (version 19.3) Enterprise Edition.

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

Prepare the Installer

-	Steps
	Make sure that all the Oracle Healthcare Foundation 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>');
	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 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 of the prerequisites are met before proceeding.
	Oracle Client Home Configuration	Specify the Oracle (version 19.3.0.0.0) client home path. The installer validates this path.
	Database Configuration	Enter values for the following fields: Host name - 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.
	Data Model Configuration	Enter values for the pre-created schemas: 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 pre-created schemas. If Oracle Healthcare Translational Research schemas exist, provide the existing schema names, otherwise provide new schema names. 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.
	Omics Data Bank and Cohort Data Mart Parameters	Enter values for the following fields. Make sure you use the same values you are currently using for: Result Partition, Promoter Offset, Flanking Offset, and Job Store Name. If you don't have existing Oracle Healthcare Translational Research schemas, then choose appropriate options. Result Partition - Used to partition result tables in the Oracle Database schema. The available options are: GENE (Default) STUDY Promoter Offset - Numerical value to specify a portion of the gene used as a promoter in the Oracle Database 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 Oracle Database 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 Oracle Database schema. It is dependent on the machine configuration of the database server. The default value is 2. Job Store Name Use the job schema name. Note: 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.