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

Accept All Unmatched Rows as Unique

Accept All Unmatched Rows as Unique

Enable (set to
) this feature to have
Informatica MDM Hub
mark as unique (CONSOLIDATION_IND=1) any records that have been through the match process, but for which no matches were identified.
If enabled, for such records,
Informatica MDM Hub
automatically changes their state to
(changes the consolidation indicator from 2 to 1). Consolidated records are removed from the data steward’s queue via the Automerge batch job.
By default, this option is disabled. In a development environment, you might want this option disabled, for example, while iteratively testing and tuning match rules to determine which records are found to be unique for a given set of match rules.
This option should always be enabled in a production environment. Otherwise, you can end up with a large number of records with a consolidation indicator of 2. If this backlog of records exceeds the Maximum Matches for Manual Consolidation setting, then you will need to process these records first before you can continue matching and consolidating other records.


We’d like to hear from you!