Table of Contents


  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Consolidation Options

Consolidation Options

You can consolidated matched records by merging. Merging (physical consolidation) combines the matched records and updates the base object. Merging occurs for merge-style base objects.
By default, base object consolidation is physically saved, so merging is the default behavior.
Merging combines two or more records in a base object table. Depending on the degree of similarity between the two records, merging is done automatically or manually.
  • Records that are definite matches are automatically merged (automerge process).
  • Records that are close but not definite matches are queued for manual review (manual merge process) by a data steward in the Merge Manager tool. The data steward inspects the candidate matches and selectively chooses matches that should be merged. Manual merge match rules are configured to identify close matches.
  • Informatica MDM Hub
    queues all other records for manual review by a data steward in the Merge Manager tool.
Match rules are configured to identify definite matches for automerging and close matches for manual merging.
To allow
Informatica MDM Hub
to automatically change the state of such records to Consolidated (thus removing them from the Data Steward’s queue), you can check (select) the
Accept all other unmatched rows as unique
check box.


We’d like to hear from you!