Performance Tuning Guide

10.4

Back Next

General Recommendations for Database

You can configure the parameters related to the database environment, virtual image environment, and database tables and data.

The following table lists the recommendations related to the database environment:

Parameter	Recommended Setting	Description
Environment Sharing	Always use non-shared environment: The Production ORS must have exclusive use of the Oracle instance. The Production Oracle instance must have exclusive use of the host machine.	The MDM Hub Oracle database instances (both the MDM Hub Master Database and ORS) need not be shared with other MDM Hub installations and must not be shared with other applications. Each additional level of sharing compromises the best performance possible on a particular hardware.
Connectivity: Application Server to Hub Store databases	The fastest connectivity possible.	Connection latency might have a major performance impact. Enable faster connectivity to the data store by using fiber optic connections.
Connectivity: Database server to Data File storage	The fastest connectivity possible.	Connection latency might have a major performance impact. Enable faster connectivity to the data by using fiber optic connections. Have a dedicated point to point connection to avoid network contention.
Database Server Sizing	Optimal database server sizing.	You need proper analysis to determine the database server sizing. Different factors including current data volume, rate of data growth, future data volume, SIF calls, and batch volume must be considered for sizing. For assistance on server sizing, contact the Informatica Professional Services team.
MDM Hub Master Database (cmx_system) host name in cluster environments	Absolute host name or IP address	To avoid caching issues in multi-node or cluster environments, use the absolute host name or IP address in place of the default localhost . The host name is configured during the MDM Hub installation. You can update the host name in the DATABASE_HOST column of the C_REPOS_DATABASE table.

The following table lists the recommendations for the virtual image environment:

Parameter	Recommended Setting	Description
Data File Storage	Use a physical drive instead of a virtualized drive.	Use a physical drive to store the data files instead of a virtualized drive within the image. Use a physical drive to avoid I/O contention because of a virtualized drive and the latency caused by the introduction of another layer with no actual benefit.
Hardware and Software Specification	As good as the equivalent physical or standalone instance.	Must be as good as the equivalent physical machine and must meet all of the PAM or sizing requirements.
CPU Cores	100% allocated to virtual image.	The physical machine, where the virtual image is hosted, must allocate 100% of the CPU cores to the virtual image. Sharing is not recommended.

The following table lists the recommendations related to the database tables and data:

Parameter	Recommended Setting	Description
Custom and Backup tables created with names starting with C_REPOS%	Do not name the custom tables or backup tables with names starting with C_REPOS% .	During HUB server restart and Met Migration, the performance of the Hub Console degrades if the schema has large volume tables with names that start with C_REPOS% . Ensure that backup tables are not created with names starting with 'C_REPOS%' .
Fragmentation	Minimize likelihood of fragmentation.	Maintain the Oracle schema to ensure that fragmentation is kept to a minimum. Monitor and de-fragment whenever the degree of fragmentation has an impact on the MDM Hub performance.
High volume of data in C_REPOS_TABLES with historical data	Perform regular maintenance on the following METADATA tables: C_REPOS_AUDIT C_REPOS_MQ_DATA_CHANGE C_REPOS_JOB_CONTROL C_REPOS_JOB_METRIC C_REPOS_MET_VALID_RESULT C_REPOS_MET_VALID_MSG C_REPOS_TASK_ASSIGNMENT_HIST	If the number of records in the metadata tables is too high, it might cause issues such as slow startup, out of memory errors, and performance issues. It is recommended to back up and truncate or reduce the data volume on the metadata tables. If you enable raw retention on any base object then you can purge C_REPOS_JOB_* tables for any date beyond the maximum raw retention period. For more information, search the Informatica Knowledge Base for article number 141201.

Rename Saved Search

Table of Contents

Performance Tuning Guide

Performance Tuning Guide

General Recommendations for Database

General Recommendations for Database