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 HotFix 3
  • 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: Glossary

Configuration Guide

Configuration Guide

Back Next

ROWID_OBJECT Survivorship

ROWID_OBJECT Survivorship

When records are merged, the MDM Hub determines which ROWID_OBJECT survives to become the ROWID_OBJECT of the merged record. Survivorship of the ROWID_OBJECT depends on how and where the records are merged. For example, how records survive after a batch merge job is different from how records survive in Informatica Data Director (IDD).
The MDM Hub handles survivorship of the ROWID_OBJECT differently in each of the following scenarios:
Batch Merge Job
During a batch merge job, the MDM Hub considers the consolidation indicator for all records. When a new record (CONSOLIDATION_IND = 4) is matched and merged with a consolidated record (CONSOLIDATION_IND = 1), the consolidated ROWID_OBJECT wins.
MDM Hub cannot predict the surviving ROWID_OBJECT for two unconsolidated records. When two new records (CONSOLIDATION_IND = 4) are matched, the record with the lowest ROWID_OBJECT wins in most cases.
Merge SIF API
When you use the Merge SIF API to merge records, the target ROWID_OBJECT wins. The target is the first record listed in the SIF request.
Informatica Data Director
When you merge records in real time in IDD, the target ROWID_OBJECT wins. The target is the record that displays in the Merge Preview column in the Match Merge Comparison view in IDD.
When you queue records for a merge, the ROWID_OBJECT of the current record that displays in IDD wins. However, survivorship in IDD also depends on the consolidation indicator for base object records. For example, if a record (CONSOLIDATION_IND = 4) is matched and merged with a consolidated record (CONSOLIDATION_IND = 1), the consolidated ROWID_OBJECT wins.
When records are queued for a merge, IDD uses entries from the underlying _MTCH table. So, to know exactly which ROWID_OBJECT survives, view the _MTCH table. The ROWID_OBJECT_MATCHED column lists the surviving ROWID_OBJECT.
0 COMMENTS
We’d like to hear from you!