Installing the Data Management Assembly without Pre-Created User Schemas
Complete the following:
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. |
|
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 tnsnames.ora file). |
|
The password expiry notification message does not display for the system user. |
|
Check write permissions on oraInventory is granted to “others”. If write permissions are not granted then add the user that the oracle software being installed to the group of the inventory owner (for instance - oinstall) as root:
|
|
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. |
|
In case of an Oracle Healthcare Foundation upgrade, back up the following csv files under
|
|
In case of an Oracle Healthcare Foundation upgrade, 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. |
Note:
The installer auto-populates some of the user parameters and lets you edit them.Prepare the Installer
- | Steps |
---|---|
|
Extract the contents of the Oracle Healthcare Foundation media pack to your system. |
|
Navigate to the media_pack_location/ folder. |
|
Unzip the
|
|
Navigate to the Disk1/install folder. |
|
Change the protection on the files as follows: chmod 755 * |
Run the Installer
Start the Oracle Universal Installer by running the following command:
- If the Oracle Data Integrator repository schemas (master and work) to be created are on
the database instance of the installation server, execute:
sh runInstaller.sh -local
- If the Oracle Data Integrator repository database or Oracle Healthcare Foundation data model database is on the database instance of
another server, 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 Management Assembly for ODI 8.2.2.0.0 option. |
|
Specify Home Details |
Enter the installation home path. |
|
Verify Installation Prerequisites |
Verify if all the prerequisites are met before proceeding. |
|
Select the Oracle Home Configuration |
Specify the Oracle client home path. |
|
Select the Oracle Data Integrator Home Location |
Specify the Oracle Data Integrator home location. The Oracle Data Integrator home should be one level above the
|
|
Select the Database Server for the Oracle Data Integrator Repository Schemas |
Select one of the following options for the Oracle Data Integrator repository schemas:
|
|
Specify Mount Path Details (applicable only for remote installations) |
Enter the configuration details for the mounted remote server directory:
To obtain the available storage drives, on the Linux machine, execute the
For example,
Note:
|
|
Specify Healthcare Data Model Database Instance Details |
Enter values for the following fields:
|
|
Specify Oracle Data Integrator Repository Database Instance Details (applicable only if you selected No in the previous screen for Select this database instance for repository schema creation) |
Enter values for the following fields:
|
|
Specify Oracle Data Integrator Supervisor Password |
Specify the supervisor password used for the Oracle Data Integrator console login. |
|
Select Terminology Loaders Source Location |
Specify the Terminology loaders source file location. This location is used to read the terminology loaders source data files. You can change this location when required. The installer creates an archive directory at the same level as the source directory. Make sure that the create directory privileges exist for the installation user. |
|
Specify Healthcare Data Model Schema Details |
Enter values for the following fields:
|
|
Specify Healthcare Data Model Schema Details |
Enter values for the following fields:
|
|
Specify Warehouse Integration Loader Details |
Enter values for the following fields:
|
|
Specify OHF Repository Schema Details |
Specify the OHF Repository schema user and password details. The Installer creates new Repository schema. |
|
Specify Healthcare Cohort Data Mart Loader Details |
Enter values for the following fields:
Specify the new schema names for the HCD configuration schema, for upgrade specify the existing HCD configuration schema name. |
|
Specify RCU Prefix and Password |
Specify an RCU prefix to be appended to the schemas created by the Oracle Data Integrator Repository Creation Utility (RCU). The RCU creates 3 schemas:
Note: The RCU Prefix must be unique. The prefix should be alphabetic only. It cannot have special characters and cannot start with a number. The length of the prefix must not exceed 8 characters. Specify a password for schemas created using the Oracle Data Integrator Repository Creation Utility (RCU). Note: The password must be between 8 and 12 alphanumeric characters long and must include at least one number. The password cannot start with a number. |
|
Specify the Tablespace Details |
Specify the tablespace names for the configuration schemas. The installer creates these tablespaces if they do not exist.
|
|
Specify the Tablespace Details |
Specify the tablespace names for repository schemas:
|
|
Specify Tablespace for Creation of Oracle Data Integrator Temporary Objects |
Specify tablespace names for the creation of temporary objects used by the Oracle Data Integrator Loaders. The installer creates these tablespaces if they do not exist.
Oracle recommends that you provide different tablespace names for each component. |
|
Specify Tablespace Location for Configuration Schemas |
Specify the tablespace location for configuration schemas. The location should be present in the data model database server with write privileges. If the Oracle Healthcare Foundation data model database is not on the installation server, you must enter the location manually. |
|
Specify Tablespace Location for Repository Schemas |
Specify the tablespace location for the Oracle Data Integrator repository schema. The location should be present in the repository database server with write privileges. If the repository database is not on the installation server, you must enter the location manually. |
|
Verify Configuration Parameters |
Click Next. |
|
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
|
|
Contact Oracle support, if necessary, to resolve any errors. |
Create a New Oracle Data Integrator Repository Login
Perform the following steps to create a new Oracle Data Integrator repository login:
- | Steps |
---|---|
|
Navigate to ODI > File > New > Create a New ODI Repository Login. |
|
Click OK. The Repository Connection Information screen is displayed. |
|
Enter the following values:
|
|
Click OK. The login name is created with the name specified in the previous step. |
|
Navigate to ODI > Connect > ODI Studio. |
|
Enter the following details:
|
Similarly, follow the above steps to create the login for the Terminology loaders, Common Data Mart loader, and Cohort Data Mart loader.