Connection latency might have a major performance impact.

You must use the fastest connectivity possible.

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.

You can update the host name in the

DATABASE_HOST

column of the

C_REPOS_DATABASE

table.

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.

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%'

.

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.

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.