Multidomain MDM
- Multidomain MDM 10.5
- All Products
Parameter
| Recommended Setting
| Description
|
---|---|---|
Environment sharing
| Always use non-shared environment:
The production ORS must have exclusive use of the database server instance.
The production database server instance must have exclusive use of the host machine.
| You must not share the MDM Hub database server instances, such as MDM Hub Master Database, ORS, and ActiveVOS database with other MDM Hub installations and applications.
Each additional level of sharing affects the performance.
|
Connectivity: Application server to the Hub Store databases, such as ping or tracert (Trace Route)
| Enable fastest connectivity to the Hub Store by using fiber-optic connections.
Run
ping and
traceroute commands from the application server to the database to verify the basic network performance.
The
traceroute command must preferably return with one hop away.
Response latency must be less than 10 milliseconds.
| Connection latency might have a major performance impact. You must use the fastest connectivity possible.
|
Connectivity: Database server to data file storage
| Enable faster connectivity to the data by using fiber-optic connections.
You must have a dedicated point-to-point connection to avoid network contention.
| Connection latency might have a major performance impact.
You must use the fastest connectivity possible.
|
Database server sizing
| To determine the database server sizing, you need proper analysis.
| You must use optimal database server sizing. You must consider the different factors, such as the current data volume, rate of data growth, future data volume, SIF or BES calls, and batch volume.
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 database 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.
|
Test specific disk partition IO
| Reasonable MB/s
| Follow the instructions in the Informatica Knowledge Base article number 139805 to test all disk partitions involved in the MDM Hub, including partitions where tablespaces reside and where the database debug log is written. If it is greater than 10 MB/s, you must fix that specific partition.
|
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:
| 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.
|