3 Oracle Healthcare Foundation Data Management Assembly for Oracle Data Integrator

This chapter describes the steps required to install the OHF Data Management Assembly for Oracle Data Integration (ODI). It contains the following sections:

Section 3.1, "Supported Upgrade Paths"
Section 3.2, "Prerequisite Checklist"
Section 3.3, "Guidelines"
Section 3.4, "Installation Log Files"
Section 3.5, "Installing the Oracle Healthcare Foundation Data Management Assembly"
Section 3.6, "Creating a New ODI Repository Login"
Section 3.7, "Upgrading to Oracle Healthcare Foundation 7.1"
Section 3.8, "Running the Installer on Pre-created Schemas"
Section 3.9, "Revoking Privileges"
Section 3.10, "Troubleshooting"
Section 3.11, "Uninstalling the Oracle Healthcare Foundation Data Management Assembly"

3.1 Supported Upgrade Paths

The following are the supported upgrade paths:

HDWF 6.1 with OHADI 3.1 installed to OHF 7.1
OHF 7.0.1 to OHF 7.1

3.2 Prerequisite Checklist

The user should be familiar with Oracle Database (DB), ODI, and Linux OS.

	Install OHF Data Model (fresh or upgrade). Follow the instructions in Chapter 2.
	ODI services can connect to the Data Model 7.1 database mentioned in the Oracle TNS file (that is, TNS entries of the required database must be available in the installation server tnsnames.ora file).
	Password expiry notification message does not display for the pre-created schemas, system user, or existing schemas (in case of upgrade).
	Installer is run on the system where ODI server is installed.
	Terminology loaders source file location exist. The installer creates an archive directory. For example, /scratch/home/oemora/TL_Source is the source file location specified during installation, which already exists. /scratch/home/oemora/TL_Archive_Files is created by the installer as the archive directory.
	Path of the data file (Configuration schema/Repository schema tablespace) mentioned while creating the tablespace is correct. Make sure that the database user should have write privileges.
	Enough space is available in the installation directory and Oracle Home directory.
	Sqlplus utility is available in the installation server and the impdp utility in the repository database server.
	Installation user should have read, write, and execute privileges to the $ODI_HOME/bin folder. The installer creates product specific files under this location.
	For remote installation (where the installation server and ODI Repository Database server are different machines, make sure that the: Remote database server directory is mounted to the installation server with an appropriate read and write privileges. Remote directories are accessible after mounting from the installation server. Linux user of the remote server, who executes the Oracle process, has the privilege of 755 to the directory (datapump). Oracle user have privilege for the mount path directory. If the repository DB exists on an Exadata machine, repository DB single node (the node which is being mounted) TNSENTRY, should be added to the tnsnames.ora file in the installation server. After installing, revert the TNSENTRY to the original entry.
	GLOBAL_NAMES database initialization parameter is set to false.

3.3 Guidelines

OUI installer does not fix any issues automatically. If the installation fails, you must verify and fix the issues before restarting the installer.
You must provide unique repository schema names. The installer imports the ETL metadata into these schemas. However, upon restarting the installer for any failures, you must specify the same values that was entered for the previous execution.
Back up the following csv files under $ODI_HOME/bin if it exist:
- bus_susp_day.csv
- daylght_svngs_day.csv
- hosp_hol_day.csv
- time_odi.csv
If the Terminology Loaders source folder is a shared folder, make sure you take a back up of the following files:
- Code Axes.txt
- Code Descriptions.txt
- Code Hierarchy.txt
- Code.txt
- Related Entity.txt
- Relations Type.txt
- Relations.txt
- Relationship Type.txt
- time.txt
Note:
If any file exists with the same name, installer will overwrite this file.
Installer auto-populates some of the user parameters and lets you edit them.

3.4 Installation Log Files

While installing the Data Management Assembly, the installer generates the following log files. When the installer is running the python script, the execution log is redirected to the below log files:

Table 3-1 Installation Log Files

File Name	Description
installActions<timestamp>.log	Records the action of the installer and can be used to diagnose issues with the installer.
oraInstall<timestamp>.out	Records the output of SQL scripts run by the installer.
oraInstall<timestamp>.err	Records the errors from the SQL scripts run by the installer. The log files are time stamped and each installation session creates a new log file. On a Linux machine, the log files are located at $ORACLE_BASE/oraInventory/logs. For example, /u01/app/oraInventory/logs.
When the installer run the `ksh` script, the execution log is redirected to the below log files:
<INSTALL_HOME>/dma_odi_master_install/dmalogs/dma_etl_install.log	Contains a consolidated log file that is archived to <INSTALL_ HOME>/dma_odi_master_install/dmalogs/tmplogs/ with the time stamp for next execution of the installer. In case of restart, logs are appended to the existing dma_etl_install.log file.
<INSTALL_HOME>/dma_odi_master_install/dmalogs/tmplogs/<script_name>.error	Contains an error file if the script is not executed successfully.
<INSTALL_HOME>/dma_odi_master_install/dmalogs/tmplogs/<script_name>.done	Indicates that the script is executed successfully.
The installer generates the following report:
<INSTALL_HOME>/reports/dma_odi_install<time_stamp>.html	Contains the installation summary of the Data Management Assembly for ODI installation.

While reporting any problems that occur during installation, make sure that you include all the above log files. Check which components were installed successfully using the following query by connecting to the enterprise schema:

Select * from W_EHA_PRODUCT_VERSION

Send the result of the query while reporting any problems to the Oracle support.

3.5 Installing the Oracle Healthcare Foundation Data Management Assembly

To install the Data Management Assembly:

Extract the contents of the OHF media pack to your system.
Navigate to the <media_pack_location>/ folder.
Unzip the OHF_V71_Linux-x64.zip file where you want to launch the installer using the following command:

unzip -a OHF_V71_Linux-x64.zip
Navigate to the Disk1/install folder.
Change the protection on files as follows:

chmod 755 *
Start the Oracle Universal Installer by running the following command:
- If the ODI repository schemas (master and work) to be created is on the database instance of the installation server, execute:
  
  sh runInstaller.sh -local
- If the ODI repository schemas (master and work) to be created is on the database instance of other 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.

The Welcome screen appears.
Click Next. The Select a Product to Install screen appears.
Select the Oracle Healthcare Foundation Data Management Assembly for ODI 7.1.0.0.0 option and click Next.

The Specify Home Details screen appears.
Enter the installation home path.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Select the Oracle Home Configuration screen appears.
Specify the Oracle client home location.
Click Next. The Select the ODI home location screen appears.
Specify the ODI home location.

Note:
ODI home should be one level above the /bin directory and should point to the /agent directory. For example, <path>/Oracle_ODI1/oracledi/agent/.
Click Next. The Select database server for ODI repository schemas screen appears.
Select one of the following options for the ODI repository schemas:
- If ODI repository database server exist on the installation server, select the Installation database server option, and go to step 19.
- Else, select the Remote database server option, and go to step 18.
(Applicable only for Remote installation) Click Next. The Specify mount path details screen appears.

Enter the following mounted directory configuration details in which remote server directory is being mounted:
- Mount path in repository database server
- Mount path in installation server
To obtain the available storage drives in the Linux machine, execute the df -h command. If the remote server directory is mounted on the installation server, the mounting is displayed as follows:
```
<Remote Server name>:<Remote server path>
        <total size>  <used up space>  <Available space>  <use%> <Path in installation server where mounting was done>
```
For example,
```
abc:/scratch/dump
         191G 138G 44G 76% /installation server
```
Note:
- (datapump) directory of the remote database server should be mounted to the installation server with an appropriate read and write privileges for the IMPDB utility (folder with dba group).
- Make sure that the remote directories are accessible after mounting from the installation server.
- If the remote server mounted path is displayed as /, provide the absolute mounted path of the remote server.
- The remote server Linux user that executes the Oracle process, must have minimum privilege of 755 to the directory.
Click Next. The Specify Healthcare Data Model database instance details screen appears.
Enter values for the following fields:
- Host name - By default, the system host name appears
- Port number
- Service name
- System user password
- Select this database instance for repository schema creation
  
  If you select Yes, the installer uses the same Data Model database instance for ODI repository schema creation. Go to step 22.
  
  If you select No, step 21 is displayed.
Click Next. The Specify ODI repository database instance details screen appears.

Enter values for the following fields:
- Host name - By default, the system host name appears
- Port
- Service name
- System user password
Click Next. The Specify ODI Supervisor password screen appears.
Specify the supervisor password used for the ODI console login.
Click Next. The Select Terminology loaders source location screen appears.
Specify the Terminology loaders source file location.

Note:
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 that of the source directory. Make sure that the create directory privileges exist for the installation user.
Click Next. The Specify Healthcare Data Model schema details screen appears.
Enter values for the following fields:
- Interface table schema name
- Interface table schema password
- Data warehouse schema name
- Data warehouse schema password
- Common data mart (hcd) schema name
- Common data mart (hcd) schema password
- Cohort data mart (cdm) schema name
- Cohort data mart (cdm) schema password
Click Next. The Specify Healthcare Data Model schema details screen appears.
Enter values for the following fields:
- Enterprise schema name
- Enterprise schema password.
Click Next. The Specify Terminology loader details screen appears.
Enter values for the following fields:
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
If you provide new schema names, the installer creates the master repository and work repository schemas, and imports loaders into it.
Click Next. The Specify Warehouse Integration loader details screen appears.
Enter values for the following fields:
- Configuration schema name
- Configuration schema password
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
If you provide new schema names, the installer creates the master repository schema and work repository schema, and imports loaders into it.

The installer creates the configuration schema if it does not exist. To upgrade, enter an existing hmc schema name.
Click Next. The Specify Healthcare common data mart loader details screen appears.
Enter values for the following fields:
- Configuration schema name
- Configuration schema password
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
If you provide new schema names, the installer creates the master repository and work repository schemas, and imports loaders into it.

The installer creates the configuration schema if it does not exist. To upgrade, enter an existing hmc schema name.
Click Next. The Specify Healthcare cohort data mart loader details screen appears.
Enter values for the following fields:
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
If you provide existing master repository schema and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
If you provide new schema names, the installer creates the master repository schema and work repository schema, and imports loaders into it.

The configuration schema is not required for CDM.
Click Next. The Specify Tablespace details screen appears.
Enter values for the following fields:

Note:
For upgrade, make sure that you enter the same tablespace names associated with the OHF 7.0.1 schemas.
- Repository schema default tablespace name
- Repository schema temporary tablespace name
- Configuration schema default tablespace name
- Configuration schema temporary tablespace name
Note:
The installer creates these tablespaces if they do not exist.
Click Next. The Specify tablespace location for configuration schema screen appears.
Specify the tablespace location for configuration schema and go to step 44.

Note:
The location should be present in the data model database server with write privileges.
Click Next. If you have selected No in the Select this database instance for repository schema creation field (step 20), this step is displayed.

The Specify tablespace location for repository schema screen appears.
Specify the tablespace location for the ODI repository schema.

Note:
The location should be present in the repository database server with write privileges.
Click Next. The Verify Configuration Parameters screens appear.
Click Next. The Summary screen appears.
Click Install.
After the installation is complete, the End of Installation screen appears.
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 on troubleshooting, see Section 3.10.
Contact Oracle support, if necessary, to resolve any errors.

3.6 Creating a New ODI Repository Login

Perform the following steps to create a new ODI repository login:

Navigate to ODI > File > New > Create a New ODI Repository Login.
Click OK. The Repository Connection Information screen is displayed.
Enter the following values:
- Login Name - For example, WIL_REPOSITORY_LOGIN
- User - SUPERVISOR
- Password - Provide the ODI Login password that was entered during installation (see Section 3.5)
- User - <database schema created for the master repository>
- Password - <database schema password created for the master repository>
- Driver List - Select OracleJDBC Driver from the drop-down list
- Driver Name - oracle.jdbc.oracledriver
- Url - Set appropriate values based on your database details
- Work Repository - Select the Work Repository option, browse to select the work repository shown (for example, for Warehouse Integration loader, select OHADI_WORK_REPOSITORY), and click OK.
Click OK. The login name is created with the name specified in step 3.
Navigate to ODI > Connect > ODI Studio.
Enter the following details:
- Login Name - Select WIL_REPOSITORY_LOGIN
- User - Supervisor
- Password - Provide the ODI login password that was entered during installation (see Section 3.5).

Similarly, follow the above steps to create the login for Terminology loaders, common data mart loader, and cohort data mart loader.

3.7 Upgrading to Oracle Healthcare Foundation 7.1

For the list of supported upgrade paths, see Section 3.1.

If any previous ETLs are in the failed status, make sure that they are execute successfully before upgrading.
Make sure that the data models of OHADI, Application Toolkit, and CDM are upgraded to OHF 7.1.
Modify the default configuration schema names to the existing configuration schema (hmc) names of OHADI and Application Toolkit.

The installer upgrades the configuration schemas to OHF 7.1.
Back up the existing hmc schemas.
Run the installer. Follow the instructions in Section 3.5.
Delete all E$_ tables under HCD schema.

3.8 Running the Installer on Pre-created Schemas

Create the following default and temporary tablespaces with an appropriate quota. The following table shows an example tablespace name:

Table 3-2 Default Tablespaces

Tablespace Details	Tablespace Name	BIG File Tablespace
Repository schema default tablespace name	odirep_ts	Yes
Repository schema temporary tablespace name	odirep_temp	Yes
Configuration schema default tablespace name	hmc_ts	Yes
Configuration schema temporary tablespace name	hmc_temp	Yes

Create the following database users and associate them with the tablespaces created above:

Terminology loader Master repository schema (tl_master_rep_71)
Terminology loader Work repository schema (tl_work_rep_71)
Warehouse Integration loader Configuration schema (wil_hmc)
Warehouse Integration loader Master repository schema (wil_master_rep_71)
Warehouse Integration loader Work repository schema (wil_work_rep_71)
Healthcare common data mart Configuration schema (hcd_hmc)
Healthcare common data mart Master repository schema (hcd_master_rep_71)
Healthcare common data mart Work repository schema (hcd_work_rep_71)
Healthcare cohort data mart Master repository schema (cdm_master_rep_71)
Healthcare cohort data mart Work repository schema (cdm_work_rep_71)

Table 3-3 Schema Names and Associated Default and Temporary Tablespaces

Schema Name	Default Tablespace	Temporary Tablespace
wil_hmc	hmc_ts	hmc_temp
hcd_hmc	hmc_ts	hmc_temp
tl_master_rep_7 1	odirep_ts	odirep_temp
tl_work_rep_7 1	odirep_ts	odirep_temp
wil_master_rep_71	odirep_ts	odirep_temp
wil_work_rep_71	odirep_ts	odirep_temp
hcd_master_rep_71	odirep_ts	odirep_temp
hcd_work_rep_71	odirep_ts	odirep_temp
cdm_master_rep_71	odirep_ts	odirep_temp
cdm_work_rep_71	odirep_ts	odirep_temp

Extract the contents of the OHF media pack to your system.
Navigate to the <media_pack_location>/ folder.
Unzip the OHF_V71_Linux-x64.zip file where you want to launch the installer using the following command:

unzip -a OHF_V71_Linux-x64.zip
Navigate to the <media_pack_location>/Disk1/stage/Components/oracle.hsgbu.hc.dma.odi/7.1.0.0.0/1/DataFiles/Expanded/filegroup1 directory.
Unzip the dma_odi_master_install.zip file.
Navigate to the dma_odi_master_install/hmc_odi_install/ directory.
Connect to the system user and execute the following scripts:
- @odi_hdi_user_privilege.sql <HDI_SCHEMA_NAME>
- @odi_hmc_user_privilege.sql <WIL_HMC_SCHEMA_NAME> <HCD_HMC_SCHEMA_NAME>
- @odi_rep_user_privilege.sql <HLI_MASTER_REP_USR> <WIL_MASTER_REP_USR> <AT_MASTER_REP_USR> <HLI_WORK_REP_USR> <WIL_WORK_REP_USR> <AT_WORK_REP_USR> <CDM_MASTER_REP_USR> <CDM_WORK_REP_USR>
Navigate to the <media_pack_location>/Disk1/install folder.
Change the protection on files as follows:

chmod 755 *
Start the Oracle Universal Installer by running the following command:
- If the ODI repository schemas (master and work) to be created is on the database instance of the installation server, execute:
  
  sh runInstaller.sh -local dba_tasks=false
- If the ODI repository schemas (master and work) to be created is on the database instance of other server, execute:
  
  sh runInstaller.sh -local remote_installation=true dba_tasks=false
where, the -local option is to install on the local node irrespective of the cluster nodes specified on the installer machine.

The Welcome screen appears.
Click Next. The Select a Product to Install screen appears.
Select the Oracle Healthcare Foundation Data Management Assembly for ODI 7.1.0.0.0 option and click Next.

The Specify Home Details screen appears.
Enter the installation home path.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Select the Oracle Home Configuration screen appears.
Specify the Oracle client home location.
Click Next. The Select the ODI home location screen appears.
Specify the ODI home location.

Note:
ODI home should be one level above the /bin directory and should point to the /agent directory. For example, <path>/Oracle_ODI1/oracledi/agent/.
Click Next. The Select database server for ODI repository schemas screen appears.
Select one of the following options for the ODI repository schemas:
- If ODI repository database server exist on the installation server, select the Installation database server option, and go to step 25.
- Else, select the Remote database server option, and go to step 24.
(Applicable only for Remote installation) Click Next. The Specify mount path details screen appears.

Enter the following mounted directory configuration details in which remote server directory is being mounted:
- Mount path in repository database server
- Mount path in installation server
To obtain available storage drives in the Linux machine, execute the df -h command. If the remote server directory is mounted on the installation server, the mounting is displayed as follows:
```
<Remote Server name>:<Remote server path>
        <total size>  <used up space>  <Available space>  <use%> <Path in installation server where mounting was done>
```
For example,
```
abc:/scratch/dump
         191G 138G 44G 76% /installation server
```
Note:
- (datapump) directory of the remote database server should be mounted to the installation server with an appropriate read and write privileges for the IMPDB utility (folder with dba group).
- Make sure that the remote directories are accessible after mounting from the installation server.
- If the remote server mounted path is displayed as /, provide the absolute mounted path of the remote server.
- The remote server Linux user that executes the Oracle process, must have minimum privilege of 755 to the directory.
Click Next. The Specify Healthcare Data Model database instance details screen appears.
Enter values for the following fields:
- Host name - By default, the system host name appears
- Port number
- Service name
- Select this database instance for repository schema creation
  
  If you select Yes, the installer uses the same Data Model database instance for the ODI repository schema creation. Go to step 28.
  
  If you select No, step 27 is displayed.
Click Next. The Specify ODI repository database instance details screen appears.

Enter values for the following fields:
- Host name - By default, the system host name appears
- Port
- Service name
Click Next. The Specify ODI Supervisor password screen appears.
Specify the supervisor password used for the ODI console login.
Click Next. The Select Terminology loaders source location screen appears.
Specify the Terminology loaders source file location.

Note:
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 that of the source directory. Make sure that the create directory privileges exist for the installation user.
Click Next. The Specify Healthcare Data Model schema details screen appears.
Enter values for the following fields:
- Interface table schema name
- Interface table schema password
- Data warehouse schema name
- Data warehouse schema password
- Common data mart (hcd) schema name
- Common data mart (hcd) schema password
- Cohort data mart (cdm) schema name
- Cohort data mart (cdm) schema password
Click Next. The Specify Healthcare Data Model schema details screen appears.
Enter values for the following fields:
- Enterprise schema name
- Enterprise schema password.
Click Next. The Specify Terminology loader details screen appears.
Enter values for the following fields:
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
Installer imports loaders into pre-created terminology loaders repository schemas.
If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
Click Next. The Specify Warehouse Integration loader details screen appears.
Enter the pre-created schema values for the following parameters:
- Configuration schema name
- Configuration schema password
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
Enter the pre-created or existing (for upgrade) configuration schema details.
The installer imports loaders into the pre-created warehouse integration loaders repository schemas. If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
Click Next. The Specify Healthcare common data mart loader details screen appears.
Enter the pre-created schema values for the following parameters:
- Configuration schema name
- Configuration schema password
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
Enter the pre-created or existing (for upgrade) configuration schema details.
The installer imports loaders into the pre-created common data mart loaders repository schemas.

If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.
Click Next. The Specify Healthcare cohort data mart loader details screen appears.
Enter the pre-created schema values for the following parameters:
- Master repository schema name
- Master repository schema password
- Work repository schema name
- Work repository schema password
Note:
The installer imports loaders into the pre-created cohort data mart loaders repository schemas.
If you provide existing master repository and work repository schema names, the installer overwrites the content with the new ones, and you will lose all existing objects.

The configuration schema is not required for CDM.
Click Next. The Specify Tablespace details screen appears.
Enter values for the following fields:
- Repository schema default tablespace name
- Repository schema temporary tablespace name
Click Next. The Verify Configuration Parameters screens appear.
Click Next. The Summary screen appears.
Click Install.
After the installation is complete, the End of Installation screen appears.
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 on troubleshooting, Section 3.10.
Contact Oracle support, if necessary, to resolve any errors.

3.9 Revoking Privileges

After the Data Management Assembly for ODI installation, run the following scripts from the user with DBA privileges:

@<OHC_Install_Home>/dma_odi_master_install/hmc_odi_install/dma_directory_drop.sql

@@<OHC_Install_Home>/dma_odi_master_install/hmc_odi_install/dma_revoke_privilege.sql <WIL_MASTER_REP_USR> <HCD_MASTER_REP_USR> <CDM_MASTER_REP_USR> <HLI_MASTER_REP_USR>

where,

<OHC_Install_Home> - OHF installation home directory

<WIL_MASTER_REP_USR> - Warehouse integration loader master repository schema name

<HCD_MASTER_REP_USR> - Healthcare common data mart loader master repository schema name

<CDM_MASTER_REP_USR> - Cohort data mart loader master repository schema name

<HLI_MASTER_REP_USR> - Terminology loader master repository schema name

3.10 Troubleshooting

For details on installation log files, see Section 3.4.

If the installer fails while executing the python script:
1. Review the logs.
2. Analyze and fix the issue.
3. Restart the installer with same installation home parameters.
For example, if the password expiry notification is displayed, reset the password and restart the installer.
If the installer fails while executing the ksh script:
1. Review the logs.
2. Analyze and fix the issue.
3. Restart the installer with same installation home parameters.
For example, if a particular directory does not have the write permission, provide the permission and restart the installer.
To skip any execution process, create a zero byte done file in the temp directory using the following steps:
1. Navigate to the following folders and select the appropriate script:
  
  <INSTALL_HOME>/dma_odi_master_install/dmascripts/
2. Remove .ksh from the file, append .done to the file, and place a zero byte file in the temp log folder.
  
  <INSTALL_HOME>/dma_odi_master_install/dmalogs/tmplogs

To perform a fresh installation with a new set of parameters, create a separate installer home directory and start the installer.

3.11 Uninstalling the Oracle Healthcare Foundation Data Management Assembly

Note:

This section is applicable only to uninstall Data Management Assembly only from the development environment.

Execute the following commands to drop user schemas by connecting to the system user. If you have installed Data Model Assembly, replace the user schema name and tablespace names with the values provided during the installation.

drop user <HCD_WORK_REP_71> cascade;
drop user <HCD_MASTER_REP_71> cascade;
drop user <WIL_WORK_REP_71> cascade;
drop user <TL_MASTER_REP_71> cascade;
drop user <CDM_WORK_REP_71> cascade;
drop user <TL_WORK_REP_71> cascade;
drop user <WIL_MASTER_REP_71> cascade;
drop user <CDM_MASTER_REP_71> cascade;
drop user <WIL_HMC71> cascade;
drop user <HCD_HMC71> cascade;
drop tablespace <hmc_temp71> INCLUDING CONTENTS and datafiles;
drop tablespace <odirep_temp71> INCLUDING CONTENTS and datafiles;
drop tablespace <odirep_ts71> INCLUDING CONTENTS and datafiles;
drop tablespace <hmc_ts71> INCLUDING CONTENTS and datafiles;
commit;

Clean up the log files at $ORACLE_BASE/oraInventory/logs.

For example, /u01/app/oraInventory/logs.