4 Oracle Healthcare Foundation Data Management Assembly for Informatica

This chapter explains how to install the Oracle Healthcare Foundation Data Management Assembly for Informatica. It contains the following sections:

Section 4.1, "Prerequisites"
Section 4.2, "Guidelines"
Section 4.3, "Installation Log Files"
Section 4.4, "Installing the Oracle Healthcare Foundation Data Management Assembly in Typical Mode"
Section 4.5, "Installing the Oracle Healthcare Foundation Data Management Assembly in Custom Mode"
Section 4.6, "Upgrading OHADI, Application Toolkit, and Cohort Data Mart Loaders to Oracle Healthcare Foundation"
Section 4.7, "Running the Installer on Pre-created Schemas"
Section 4.8, "Revoking Privileges"
Section 4.9, "Troubleshooting"
Section 4.10, "Uninstalling the Oracle Healthcare Foundation Data Management Assembly"

4.1 Prerequisites

Before installing Oracle Healthcare Foundation, complete the following pre-installation tasks. The user should be familiar with the Oracle Database (DB), Informatica, and Linux OS.

Install Oracle Healthcare Foundation Data Model (fresh or upgrade). Follow the instructions in Chapter 2.
Make sure that the Informatica domain is running and no user is connected to the Informatica Admin Console.
Make sure that the Informatica services can connect to the Data Model 7.0.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).
Make sure that you can connect the database using EZCONNECT syntax. For example, sqlplus <user>/<password>@<hostname>:<port>/<service name>
Make sure that the password expiry notification message does not display for the pre-created schemas, system user, or existing schemas (in case of upgrade).
Installer must run on the system where Informatica Server is installed for Data Management Assembly installation.
The terminology loaders source file location should exist before the installation starts. 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 at the same level as the TL_Source folder.
Make sure that the 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.
Make sure that there is enough space 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.
Make sure that the installation user should have read, write, and execute privileges to the following folder:

$INFA_HOME/server/infa_shared/SrcFiles

The installer creates product-specific folders and parameter files under this location.
For remote installation (where the installation server and Informatica Repository Database are on 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).
- 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.
Set the GLOBAL_NAMES database initialization parameter to false.

4.2 Guidelines

OUI installer does not fix any issues automatically. If the installation fails, you must manually verify, and fix the issues.
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 you entered for the previous execution.
Back up the following csv files under $INFROMATICA_HOME/server/infa_shared/SrcFiles if it exists:
- bus_susp_day.csv
- daylght_svngs_day.csv
- hosp_hol_day.csv
- time_am.csv
- time_pm.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.

4.3 Installation Log Files

While installing Oracle Healthcare Foundation 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:

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 is running the ksh script, the execution log is redirected to the below log files:

<INSTALL_HOME>/dma_infa_master_install/dmalogs/dma_etl_install.log - Contains a consolidated log file that is archived to <INSTALL_HOME>/ dma_infa_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_infa_master_install/dmalogs/tmplogs/<script_name>.error - Contains an error file if the script is not executed successfully.
<INSTALL_HOME>/dma_infa_master_install/dmalogs/tmplogs/<script_name>.done - Indicates that the script is executed successfully.

The installer generates the following reports:

ORACLE_HOME/reports/dma_infa_custom_install<time_stamp>.html - Contains the installation summary of the Data Management Assembly for Informatica custom installation.
ORACLE_HOME/reports/dma_infa_typical_install<time_stamp>.html - Contains the installation summary of the Data Management Assembly for Informatica typical 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.

4.4 Installing the Oracle Healthcare Foundation Data Management Assembly in Typical Mode

To install the Oracle Healthcare Foundation Data Management Assembly in typical mode, perform the following:

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

unzip -a OHF_V701_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:
- Database server is on the machine where the installer is running, execute:
  
  sh runInstaller.sh -local
- 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.

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

The Specify Home Details screen appears.
Enter or select the path where you want to install.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Oracle Home Configuration screen appears.
Enter the Oracle client home location.
Click Next. The Select the Informatica home location screen appears.
Specify the Informatica home location.

Note:
Informatica home should be one level above the /server directory. For example, <path>/Informatica/961/.
Click Next. The Select database server for Informatica repository schemas screen appears.
Select one of the following options for the Informatica repository schemas:
- If Informatica repository database server exist on the installation server, select the Installation database server option, and go to step 20 .
- Else, select the Remote database server option, and go to step 19.
(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.
- 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 a 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:
- Hostname - By default, the system host name appears
- Port number
- Service name
- System user password
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 Warehouse Integration loader details screen appears.
Enter values for the following fields:
- Configuration schema password
- Repository schema password
Note:
The installer creates a configuration schema (wil_hmc) and repository schema (wil_rep_701), and imports loaders into it.
The installer creates a repository service with Warehouse_Integration_Loaders_701 and integration service with Is_Warehouse_Integration_Loaders_701.
Click Next. The Specify Healthcare common data mart loader details screen appears.
Enter values for the following fields:
- Configuration schema password
- Repository schema password
Note:
The installer creates a configuration schema (hcd_hmc) and repository schema (hcd_rep_701), and imports loaders into it.
Installer creates a repository service with Common_Datamart_Loaders_701 and integration service with Is_Common_Datamart_Loaders_701.
Click Next. The Specify Healthcare cohort data mart loader details screen appears.
Enter value for the following parameter:
- Repository schema password
Note:
The installer creates a repository schema (cdm_rep_701) and imports loaders into it.
The installer creates a repository service with Cohort_Datamart_Loaders_701 and integration service with Is_Cohort_Datamart_Loaders_701.

The configuration schema is not required for CDM.
Click Next. The Specify tablespace location for configuration schema screen appears.
Specify the tablespace location for configuration schema.

Note:
The location should be present in the data model database server with write privileges.

Click Next. The Specify Informatica Domain Details.

Domain name
Domain code page ID
Node name
License name
Informatica host name
Informatica port number
Informatica administrator user name
Informatica administrator password

Contact your Informatica administrator for Domain Code Page ID and provide a valid Code Page ID. Make sure that code page is compatible with the domain code page for creating the integration service. For a domain compatible code page, see any existing and active integration service code pages from the Informatica admin console. A list of sample code pages and their IDs are as follows:

Table 4-1 Sample Code Pages and their IDs

Name	Description	ID
US-ASCII	7-bit ASCII	1
Latin1	ISO 8859-1 Western European	4
JapanEUC	Japanese Extended UNIX Code (including JIS X 0212)	18
UTF-8	Unicode Transformation Format, multibyte	106
MS932	MS Windows Japanese, Shift-JIS	2024
MS1252	MS Windows Latin1 (ANSI), superset of Latin1	2252

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 4.9.
Contact Oracle support, if necessary, to resolve any errors.

4.5 Installing the Oracle Healthcare Foundation Data Management Assembly in Custom Mode

To install the Oracle Healthcare Foundation Data Management Assembly in custom mode, perform the following:

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

unzip -a OHF_V701_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 Informatica repository schemas to be created is on the database instance of the installation server, execute:
  
  sh runInstaller.sh -local
- If the Informatica repository schemas 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 Informatica 7.0.1.0.0 option.
Select the Custom option and click Next.

The Specify Home Details screen appears.
Enter or select the path where you want to install.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Oracle Home Configuration screen appears.
Enter the Oracle client home location.
Click Next. The Select the Informatica home location screen appears.
Specify the Informatica home location.

Note:
Informatica home should be one level above the /server directory. For example, <path>/Informatica/961/.
Click Next. The Select database server for Informatica repository schemas screen appears.
Select one of the following options for the Informatica repository schemas:
- If Informatica repository database server exist on the installation server, select the Installation database server option, and go to step 20.
- For remote installation, select the Remote database server option, and go to step 19.
(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 - Remote server path
- Mount path in installation server - Path in the installation server where the mounting is performed
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.
- 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 Informatica repository schema creation. Go to step 24.
  
  If you select No, the Specify Informatica repository database instance details screen is displayed (step 22).
Click Next. The Specify Informatica repository 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
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 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 Warehouse Integration loader details screen appears.
Enter values for the following fields:
- Configuration schema name
- Configuration schema password
- Repository name
- Repository schema name
- Repository schema password
Note:
Provide a repository schema that is not present in the repository database instance. The installer creates repository schema and imports loaders into it.
The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>).

The installer creates a configuration schema if it does not exist.

For upgrade, provide an existing HMC schema.
Click Next. The Specify Healthcare common data mart loader details screen appears.
Enter values for the following fields:
- Configuration schema name
- Configuration schema password
- Repository name
- Repository schema name
- Repository schema password
Note:
Provide a repository schema that is not present in the repository database instance. The installer creates a repository schema and imports loaders into it.
The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>).

The installer creates a configuration schema if it does not exist.

For upgrade, provide an existing HMC schema.
Click Next. The Specify Healthcare cohort data mart loader details screen appears.
Enter value for the following parameter:
- Repository name
- Repository schema name
- Repository schema password
Note:
Provide a repository schema that is not present in the repository database instance. The installer creates a repository schema and imports loaders into it.
The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>).

The configuration schema is not required for CDM.
Click Next. The Specify Tablespace details screen appears.
Enter value for the following parameter:
- 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 in the database.
Click Next. The Specify tablespace location for configuration schema screen appears.
Specify the configuration schema tablespace location.
Click Next. If you have selected No in the Select this database instance for repository schema creation field (step 21), this step is displayed.

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

Click Next. The Specify Informatica Domain Details.

Domain name
Domain code page ID
Node name
License name
Informatica host name
Informatica port number
Informatica administrator user name
Informatica administrator password

Contact your Informatica Administrator for the Domain Code Page ID and provide a valid Code Page ID. Make sure that the code page is compatible with domain code page for creating the Integration Service. For a domain compatible code page, see any existing and active integration service code pages from the Informatica admin console. A list of sample code pages and their IDs are as follows:

Table 4-2 Sample Code Pages and their IDs

Name	Description	ID
US-ASCII	7-bit ASCII	1
Latin1	ISO 8859-1 Western European	4
JapanEUC	Japanese Extended UNIX Code (including JIS X 0212)	18
UTF-8	Unicode Transformation Format, multibyte	106
MS932	MS Windows Japanese, Shift-JIS	2024
MS1252	MS Windows Latin1 (ANSI), superset of Latin1	2252

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 4.9.
Contact Oracle support, if necessary, to resolve any errors.

4.6 Upgrading OHADI, Application Toolkit, and Cohort Data Mart Loaders to Oracle Healthcare Foundation

To upgrade existing OHADI 3.1, Application Toolkit 3.1, and CDM 3.1 to Oracle Healthcare Foundation Data Management Assembly 7.0.1, perform the following steps:

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 Oracle Healthcare Foundation 7.0.1.
The OUI displays default configuration schema (hmc) names. You must change these schema names to existing schema names of OHADI 3.1 and Application Toolkit 3.1.

The installer upgrades the configuration schemas to Oracle Healthcare Foundation 7.0.1.
The loader jobs (ETLs) are imported into a fresh repository. Therefore, enter unique names for the repository names and repository schema names.

Note:
If an existing repository names and repository schema names are entered, the installer may terminate or delete the objects.
Run the installer in the custom mode. Follow the instructions in Section 4.5.

4.7 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 4-3 Default Tablespaces

Tablespace Details	Tablespace Name	BIG File Tablespace
Repository schema default tablespace name	infarep_ts	Yes
Repository schema temporary tablespace name	infarep_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:

Warehouse Integration loader Configuration schema (wil_hmc)
Warehouse Integration loader Repository schema (wil_rep_701)
Healthcare common data mart Configuration schema (hcd_hmc)
Healthcare common data mart Repository schema (hcd_rep_701)
Healthcare cohort data mart Repository schema (cdm_rep_701)

Table 4-4 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
wil_rep_701	infarep_ts	infarep_temp
hcd_rep_701	infarep_ts	infarep_temp
cdm_rep_701	infarep_ts	infarep_temp

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

unzip -a OHF_V701_Linux-x64.zip
Navigate to the directory <media_pack_location>/Disk1/stage/Components/oracle.hsgbu.hc.dma.infa/7.0.1.0.0/1/DataFiles/ Expanded/filegroup1.
Unzip the dma_infa_master_install.zip file.
Navigate to the dma_infa_master_install/hmc_infa_install directory.
Connect to the system user and execute the following scripts:
- @infa_hdi_user_privilege.sql <HDI_SCHEMA_NAME>
- @infa_hmc_user_privilege.sql <WIL_HMC_SCHEMA_NAME> <HCD_HMC_SCHEMA_NAME>
- @infa_rep_user_privilege.sql <WIL_INFA_REP_DB_USER> <HCD_INFA_REP_DB_USER> <CDM_INFA_REP_DB_USER>
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 Informatica repository schemas to be created is on the database instance of the installation server, execute:
  
  sh runInstaller.sh -local dba_tasks=false
- If the Informatica repository schemas 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 Informatica 7.0.1.0.0 option.
Select the Custom option and click Next.

The Specify Home Details screen appears.
Enter or select the path where you want to install.
Click Next. The Verify Installation Prerequisites screen appears.
Verify if all the prerequisites are met before proceeding.
Click Next. The Oracle Home Configuration screen appears.
Enter the Oracle client home location.
Click Next. The Select the Informatica home location screen appears.
Specify the Informatica home location.

Note:
Informatica home should be one level above the /server directory. For example, <path>/Informatica/961/.
Click Next. The Select database server for Informatica repository schemas screen appears.
Select one of the following options for Informatica repository schemas:
- If the Informatica repository database server exist on the installation server, select the Installation database server option, and go to step 26.
- Else, select the Remote database server option, and go to step 25.
(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 - Remote server path
- Mount path in installation server - Path in the installation server where the mounting is performed
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.
- 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 Informatica repository schema creation. Go to step 30.
  
  If you select No, the Specify Informatica repository database instance details screen is displayed (step 28).
Click Next. The Specify Informatica repository database instance details screen appears.
Enter values for the following fields:
- Host name - By default, the system host name appears
- Port number
- Service name
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 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 Warehouse Integration loader details screen appears.
Enter the pre-created schema details for the following parameters:
- Configuration schema name
- Configuration schema password
- Repository name
- Repository schema name
- Repository schema password
Note:
The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>).
For upgrade, provide an existing or pre-created hmc schema details.
Click Next. The Specify Healthcare common data mart loader details screen appears.
Enter the pre-created schema details for the following parameters:
- Configuration schema name
- Configuration schema password
- Repository name
- Repository schema name
- Repository schema password
Note:
The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>).
For upgrade, provide an existing or pre-created hmc schema details.
Click Next. The Specify Healthcare cohort data mart loader details screen appears.
Enter the pre-created schema details for the following parameters:
- Repository name
- Repository schema name
- Repository schema password
Note:
The installer creates a repository service (<Repository name>) and integration service (Is_<Repository name>).
The configuration schema is not required for CDM.
Click Next. The Specify Tablespace details screen appears.
Enter the pre-created schema details for the following parameters:
- Repository schema default tablespace name
- Repository schema temporary tablespace name

Click Next. The Specify Informatica Domain Details.

Domain name
Domain code page ID
Node name
License name
Informatica host name
Informatica port number
Informatica administrator user name
Informatica administrator password

Contact your Informatica Administrator for the Domain Code Page ID and provide a valid Code Page ID. Make sure that the code page is compatible with the domain code page for creating Integration Service. For a domain compatible code page, see any existing and active integration service code pages from the Informatica admin console. A list of sample code pages and their IDs are as follows:

Table 4-5 Sample Code Pages and their IDs

Name	Description	ID
US-ASCII	7-bit ASCII	1
Latin1	ISO 8859-1 Western European	4
JapanEUC	Japanese Extended UNIX Code (including JIS X 0212)	18
UTF-8	Unicode Transformation Format, multibyte	106
MS932	MS Windows Japanese, Shift-JIS	2024
MS1252	MS Windows Latin1 (ANSI), superset of Latin1	2252

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 4.9.
Contact Oracle support, if necessary, to resolve any errors.

4.8 Revoking Privileges

After the Data Management Assembly for Informatica installation, run the following scripts from System user:

@<OHC_Install_Home>/dma_infa_master_install/hmc_infa_install/dma_directory_drop.sql

@<OHC_Install_Home>/dma_infa_master_install/hmc_infa_install/dma_revoke_privilege.sql <WIL_INFA_REP_DB_USER> <HCD_INFA_REP_DB_USER> <CDM_INFA_REP_DB_USER>

where,

<OHC_Install_Home> is Oracle Healthcare Foundation installation home directory

<WIL_INFA_REP_DB_USER> is Warehouse integration loader repository schema name

<HCD_INFA_REP_DB_USER> is Healthcare common data mart loader repository schema name

<CDM_INFA_REP_DB_USER> is Cohort data mart loader repository schema name

4.9 Troubleshooting

For details on installation log files, see Section 4.3.

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_infa_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_infa_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.

4.10 Uninstalling the Oracle Healthcare Foundation Data Management Assembly

Note:

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

Custom Mode

Execute the following commands to drop user schemas by connecting to the system user.

drop user <WIL_HMC_USR>  cascade;
drop user <WIL_INFA_REP_DB_USER>  cascade;
drop user <AT_HMC_USR>  cascade;
drop user <AT_INFA_REP_DB_USER>  cascade;
drop user <CDM_INFA_REP_DB_USER> cascade;
drop tablespace <INFA_REP_TBSP> INCLUDING CONTENTS and datafiles;
drop tablespace <INFA_REP_TMP_TBSP> INCLUDING CONTENTS and datafiles;
drop tablespace <HMC_SCHEMA_TBSP> INCLUDING CONTENTS and datafiles;
drop tablespace <HMC_SCHEMA_TMP_TBSP> INCLUDING CONTENTS and datafiles;
commit;

Log in to the Informatica Admin console and delete the following repositories and integration services:

Repositories:
- <WIL_REP_NAME>
- <AT_REP_NAME>
- <CDM_REP_NAME >
Integration Services:
- <WIL_INT_SRVC >
- <AT_INT_SRVC >
- <CDM_INT_SRVC>

Note:

Ensure that there are no db (.dbf files) files in <INSTALL_HOME>.

If they exist, do not execute the following command:

rm -r <INSTAL_HOME>

Contact the Database Administrator for guidance.
Back up any user-specific files (apart from installer default files) in the installation directory.

Typical Mode

Execute the following commands to drop user schemas by connecting to the system user.

drop user wil_hmc cascade;
drop user wil_rep_701 cascade;
drop user hcd_hmc cascade;
drop user hcd_rep_701 cascade;
drop user cdm_rep_701 cascade;
drop tablespace infarep_ts INCLUDING CONTENTS and datafiles;
drop tablespace infarep_temp INCLUDING CONTENTS and datafiles;
drop tablespace hmc_ts INCLUDING CONTENTS and datafiles;
drop tablespace hmc_temp INCLUDING CONTENTS and datafiles;
commit;

Log in to the Informatica Admin console and delete the following repositories and integration services:

Repositories:
- Warehouse_Integration_Loaders_701
- Common_Datamart_Loaders_701
- Cohort_Datamart_Loaders_701
Integration Services:
- Is_Warehouse_Integration_Loaders_701
- Is_Common_Datamart_Loaders_701
- Is_Cohort_Datamart_Loaders_701

Note:

Ensure that there are no db (.dbf files) files in <INSTALL_HOME>.

If they exist, do not execute the following command:

rm -r <INSTAL_HOME>

Contact the Database Administrator for guidance.
Back up any user-specific files (apart from installer default files) in the installation directory.