Check Prerequisites
- | Steps |
---|---|
The user is familiar with Oracle Database (DB), Oracle Data Integrator, and Linux OS. |
|
The Oracle Healthcare Foundation Data Model is installed. Follow the
instructions in |
|
The Data Management Assembly installer is run on the system where the Oracle Data Integrator server is installed. |
|
Make sure that the database compatible parameter is set to 19.3.0.0.0 by connecting to the DBA user and running the query below:
If the parameter is not set to 19.3.0.0.0, ask your database administrator to set it. |
|
Be sure to backup all custom database objects and custom ETL objects before initiating the Oracle Healthcare Foundation upgrade. Import the custom database objects and custom ETLs into the upgraded environment. |
|
Oracle Healthcare Foundation uses separate HMC schemas for the WIL and HCD loaders. If you have a common HMC schema for OHADI (WIL) and HCD, designate different HMC schemas for WIL (the existing HMC) and HCD (the new HMC_HCD) by performing the following steps:
|
|
Oracle Data Integrator services can connect to the Data Model 8.2.2 database mentioned
in the Oracle TNS file (TNS entries of the required database must be available
in the installation server |
|
The password expiry notification message does not display for the system user or existing schemas. |
|
The terminology loaders source file location exists. The installer creates an archive directory. For example,
|
|
The path of the data file (Configuration schema/Repository schema tablespace) mentioned when creating the tablespace is correct. Make sure that the database user has write privileges. |
|
Enough space is available in the installation directory and the Oracle Home directory. |
|
The Sqlplus utility is available on the installation server. |
|
The impdp utility is available on the repository database server. |
|
The installation user has
read, write, and execute privileges to the
|
|
For remote installations, where the installation server and the Oracle Data Integrator Repository Database server are different machines, make sure that:
|
|
GLOBAL_NAMES database initialization parameter is set to false. |
|
Back up the following csv
files under
|
|
If the Terminology Loaders source folder is shared, make a backup of the following files:
The installer will overwrite any existing files from the list above. |
|
If any previous ETLs are in the failed status, make sure that they execute successfully before upgrading. |
|
Make sure that the data models are upgraded to Oracle Healthcare Foundation 8.2.2. |
|
The OUI displays default configuration schema (hmc) names. You must change these schema names to the existing hmc schema names. The installer upgrades the configuration schemas to Oracle Healthcare Foundation 8.2.2. |
|
Back up the existing hmc schemas. |
Note:
The installer auto-populates some of the user parameters and lets you edit them.