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

Tables Associated with the Load Process

Tables Associated with the Load Process

In addition to base objects, the staging table, cross-reference table, history tables, and reject table in the
Hub Store
are associated with the load process.
The following tables are associated with the load process:
staging table
Contains the data that was accepted and copied from the landing table during the stage process.
cross-reference table
Used for tracking the lineage of data—the source system for each record in the base object. For each source system record that is loaded into the base object,
Informatica MDM Hub
maintains a record in the cross-reference table that includes:
  • an identifier for the system that provided the record
  • the primary key value of that record in the source system
  • the most recent cell values provided by that system
Each base object record will have one or more cross-reference records.
history tables
If history is enabled for the base object, and records are updated or inserted, then the load process writes to this information into two tables:
  • base object history table
  • cross-reference history table
reject table
Contains records from the staging table that the load process has rejected for a specific reason. Rejected records will not be loaded into base objects. The reject table is associated with the staging table (called stagingTableName_REJ). Rejected records can be inspected after running Load jobs.
Informatica MDM Hub increases performance by rejecting a record when it first encounters a reason to reject the record. The reject table describes one reason why Informatica MDM Hub rejected a record. If there is more than one reason for Informatica MDM Hub to reject a record, the reject table describes the first reason that Informatica MDM Hub encounters.


We’d like to hear from you!