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

Rejected Records in Load Jobs

Rejected Records in Load Jobs

During the load process, records in the staging table might be rejected for the following reasons:
  • future date or NULL date in the LAST_UPDATE_DATE column
  • LAST_UPDATE_DATE less than 1900
  • NULL value mapped to the PKEY_SRC_OBJECT of the staging table
  • duplicates found in PKEY_SRC_OBJECT
  • invalid value in the HUB_STATE_IND field (for state-enabled base objects only)
  • invalid or NULL foreign keys.
Rejected records will not be loaded into base objects. Rejected records can be inspected after running Load jobs.
To reject records, the load process requires traceability back to the landing table. If you are loading a record from a staging table and its corresponding record in the associated landing table has been deleted, then the load process does not insert it into the reject table.


We’d like to hear from you!