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

Immutable Rowid Object

Immutable Rowid Object

For a given base object, you can designate a source system as an immutable source, which means that records from that source system are accepted as unique (CONSOLIDATION_IND = 1), even in the event of a merge. Once a record from that source is fully consolidated, it is not changed subsequently, nor is it matched to any other record (although other records can be matched to it). Only one source system can be configured as an immutable source.
If the Requeue on Parent Merge setting for a child base object is set to UNCONSOLIDATED ONLY, in the event of a merging parent, the consolidation indicator is set to 4 for the child record, except for records with consolidation indicator set to 1. To requeue child records with consolidation indicator set to 1, the Requeue on Parent Merge setting must be manually set to 2.
Immutable sources are also distinct systems. All records are stored in the
Informatica MDM Hub
as master records. For all source records from an immutable source system, the consolidation indicator for Load and PUT is always 1 (consolidated record).
To specify an immutable source for a base object, click the drop-down list next to Immutable Rowid Object and select a source system.
This list displays the source system(s) associated with this base object. Only one source system can be designated an immutable source system.
Immutable source systems are applicable when, for example,
Informatica MDM Hub
is the only persistent store for the source data. Designating an immutable source system streamlines the load, match, and merge processes by preventing intra-source matches and automatically accepting records from immutable sources as unique. If two immutable records must be merged, then a data steward needs to perform a manual verification in order to allow that change. At that point,
Informatica MDM Hub
allows the data steward to choose the key that remains.


We’d like to hear from you!