11 Data Management Assembly for Informatica Upgrade

Follow the instructions in Chapter 2, "Data Model Installation" or Chapter 9, "Data Model Upgrade".

select * from v$parameter where name = 'compatible';

If the parameter is not set to 12.1.0.2.0, ask your database administrator to set it.

1. Create a new HMC schema for HCD loaders. For example: HMC_HCD.

2. Provide the newly created HMC_HCD schema with the same privileges as the existing HMC schema.

3. Move the HCD* tables from the existing HMC schema to the new HMC_HCD schema and remove them from existing HMC schema.

/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 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 privilege 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.

• bus_susp_day.csv

• daylght_svngs_day.csv

• hosp_hol_day.csv

• time_am.csv

• time_pm.csv

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

The installer upgrades the configuration schemas to OHF 7.1.1.

unzip -a OHF_V711_Linux-x64.zip

chmod 755 *

The Informatica home should be one level above the /server directory. For example, <path>/Informatica/961/.

• If the Informatica repository database server is on the installation server, select the Installation database server option, and skip the next step.

• For remote installations, select the Remote database server option, and go to the next step.

• Mount path in the repository database server - Remote server path

• Mount path in the installation server - Path on the installation server where the mounting is performed

To obtain the available storage drives, on 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:

• The (datapump) directory of the remote database server should be mounted to the installation server with 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.

• Host name - By default, the system host name appears. For remote installations, set this value to the host name of the remote machine.

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

• Host name - By default, the system host name appears. For remote installations, set this value to the host name of the remote machine.

• Port

• Service name

• System user password

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.

• 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

• Enterprise schema name

• Enterprise schema password.

• Configuration schema name

• Configuration schema password

• Repository name

• Repository schema name

• Repository schema password

Provide an existing HMC schema.

If you provide an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>).

The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose all existing objects.

• Configuration schema name

• Configuration schema password

• Repository name

• Repository schema name

• Repository schema password

Specify an existing HMC schema.

If you provide an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>).

The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose all existing objects.

Enter values for the following fields:

• Repository name

• Repository schema name

• Repository schema password

If you enter an existing repository name, the installer removes the repository and the corresponding integration service (Is_<Repository name>). It creates a repository service (<Repository name>) and integration service (Is_<Repository name>).

The installer creates a repository schema if it does not exist in the database. If you enter an existing repository schema, the installer overwrites the content with the new one, and you will lose the existing objects.

The configuration schema is not required for CDM.

• Configuration schema default tablespace name

• Configuration schema temporary tablespace name

• Repository schema default tablespace name

• Repository schema temporary tablespace name

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

If the OHF data model database is not on the installation server, you must enter the location manually.

When the repository database is not on the installation server, you must enter the location manually.

The location should be present on the repository database server with write privileges.

• 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 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:

• US-ASCII (ID 1) - 7-bit ASCII

• Latin1 (ID 4) - ISO 8859-1 Western European

• JapanEUC (ID 18) - Japanese Extended Unix Code (including JIS X 0212)

• UTF-8 (ID 106) - Unicode Transformation Format, multibyte

• MS932 (ID 2024) - MS Windows Japanese, Shift-JIS

• MS1252 (ID 2252) - MS Windows Latin1 (ANSI), superset of Latin1