Check Prerequisites

-	Steps
	The user is familiar with Oracle Database (DB), Informatica, and Linux OS.
	The Oracle Healthcare Foundation Data Model is installed. Follow the instructions in Data Model Installation or Data Model Upgrade.
	Make sure that the database compatible parameter is set to 12.2.0.1.0 or higher by connecting to the DBA user and running the query below: select * from v$parameter where name = 'compatible'; If the parameter is not set to 12.2.0.1.0 or higher, 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: Create a new HMC schema for HCD loaders. For example: HMC_HCD. Provide the newly created HMC_HCD schema with the same privileges as the existing HMC schema. Move the HCD* tables from the existing HMC schema to the new HMC_HCD schema and remove them from the existing HMC schema.
	The Informatica domain is running and no user is connected to the Informatica Admin Console.
	Informatica services can connect to the Data Model 7.3 database mentioned in the Oracle TNS file (TNS entries of the required database must be available in the installation server tnsnames.ora file).
	You can connect the database using EZCONNECT syntax. For example, sqlplus user/password@hostname:port/service name.
	The password expiry notification message does not display for the system user or the existing schemas.
	The installer is run on the system where the Informatica server is installed.
	The terminology loaders source file location exists. 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.
	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 $INFA_HOME/server folder. The installer creates product-specific folders and parameter files under this location.
	For remote installations, where the installation server and the Informatica Repository Database are on different machines, make sure that: The remote database server directory is mounted to the installation server with appropriate read and write privileges. The remote directories are accessible after mounting from the installation server. The Linux user of the remote server, who executes the Oracle process, has privilege 755 for the directory (datapump). The Oracle user has privileges for the mount path directory. If the repository DB is on an Exadata machine, the repository DB single node (the node which is mounted) TNSENTRY should be added to the tnsnames.ora file on the installation server. After installation, revert TNSENTRY to the original entry.
	GLOBAL_NAMES database initialization parameter is set to false.
	Back up the following csv files under $INFORMATICA_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 shared, make a backup 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 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.1.
	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.1.
	Back up the existing hmc schemas.