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: Glossary

Dirty Table

Dirty Table

All base objects have an associated dirty table named <
base object name
>_DRTY, which is a system table. The dirty table has a ROWID_OBJECT column, which identifies the base object records for which match tokens need to be generated. The MDM Hub stores the match tokens in the match key table.
For each unique ROWID_OBJECT in the dirty table, the tokenize process generates match tokens, and then cleans up the dirty table.
The MDM Hub updates the dirty table during the following sequence of batch processes:
  1. Load. The MDM Hub loads new records or updates existing records. The MDM Hub populates the dirty table with the ROWID_OBJECT values of the new records or updated records for which match column values change.
  2. Tokenize. The MDM Hub generates the match keys. The MDM Hub removes the ROWID_OBJECT values of records that are tokenized from the dirty table.
  3. Match. The MDM Hub identifies matches. The dirty table remains unchanged.
  4. Consolidate. The MDM Hub consolidates the matched records. The MDM Hub populates the dirty table with the ROWID_OBJECT values of the new records or updated records for which match column values change.
  5. Tokenize. The MDM Hub generates the match keys. The MDM Hub removes the ROWID_OBJECT values of records that are tokenized from the dirty table.

0 COMMENTS

We’d like to hear from you!