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

Preserve Source System Keys

Preserve Source System Keys

During load jobs, the MDM Hub can generate primary keys or use primary keys from a source system. The MDM Hub can preserve the source system keys for one source system for the data loads.
When you add a staging table to a base object, specify whether the MDM Hub must use primary key values from the source system or use the primary key values that the MDM Hub generates. If you enable the option to preserve source system keys, during load jobs, the MDM Hub takes the primary key values of a source system in the PKEY_SOURCE_OBJECT column of the staging table and inserts the value into the ROWID_OBJECT column in the target base object. Also, if you enable the option to preserve source system keys, the MDM Hub does not generate primary keys for the records that you want to load into base objects.
Before you enable the option to preserve source system keys, consider the following MDM Hub behaviors:
  • After a staging table is created, you cannot change the setting to preserve source system keys.
  • One staging table in each base object can have the option to preserve source system keys enabled even if it is from the same source system. The reserved key range is set at the initial load only.
  • During the load process, if multiple records contain the same PKEY_SRC_OBJECT value, the surviving record is the one with the most recent LAST_UPDATE_DATE. The other records move to the rejects table.
  • When the first record loads for the source system for which you enable the option to preserve source system keys, the MDM Hub reserves the highest reserved key.
  • To ensure that the MDM Hub preserves all source system keys up to the highest reserved key, load the source system that is enabled with the option to preserve source system keys before you load other source systems.
  • If a record contains a source system key that is in use by another source system and has a value that is lower than the highest reserved key, the load job does not process the current record block and generates a warning.
  • A non-numeric ROWID_OBJECT is not supported by the MDM Hub. The MDM Hub uses a ROWID_OBJECT that the MDM Hub generates for non-numeric source system keys.


We’d like to hear from you!