Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Multidomain MDM 10.4
  • All Products

Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Configuration Guide

Configuration Guide

Back Next

MDM Hub Stage Process Tables

MDM Hub Stage Process Tables

The
MDM Hub
 stage process uses the landing table, staging table, raw table, and reject table to move data from the source system to the
MDM Hub
.
The
MDM Hub
 stage process uses the following
MDM Hub
 tables:
Landing table
An
MDM Hub
 table that contains data that is initially loaded from a source system. The
MDM Hub
 uses data in a landing table for the
MDM Hub
 stage process.
Staging table
An
MDM Hub
 table that contains data that the
MDM Hub
 accepts during the stage process. During the An
MDM Hub
 stage process data moves from the landing tables to the staging tables.
Raw table
An
MDM Hub
 table that contains raw data that the
MDM Hub
 archives from the landing tables. Each raw table is associated with a staging table and is named <staging table name>_RAW. You can configure the
MDM Hub
 to archive raw data after a certain number of data loads or after a certain time interval. The
MDM Hub
 inserts null primary keys even when the landing table has not changed.
Reject table
An
MDM Hub
 table that contains records that the
MDM Hub
 rejects and a description of the reason for each reject. Each reject table is associated with a staging table and is named <staging table name>_REJ. The
MDM Hub
 generates a reject table for each staging table that you create. The
MDM Hub
 inserts null primary keys even when the landing table has not changed.
The
MDM Hub
 rejects records during the stage process for the following reasons:
  • The LAST_UPDATE_DATE column contains a future date or null date.
  • The LAST_UPDATE_DATE column value is less than 1900.
  • A null value is mapped to the PKEY_SRC_OBJECT column of the staging table.
  • The PKEY_SRC_OBJECT column contains duplicates. If the
    MDM Hub
     finds multiple records with the same PKEY_SRC_OBJECT value, the
    MDM Hub
     loads the record with the highest SRC_ROWID value. The
    MDM Hub
     moves the other records to the reject table.
  • The HUB_STATE_IND field contains a value that is not valid for a base object for which state management is enabled.
  • A unique column contains duplicates.
0 COMMENTS
We’d like to hear from you!