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. When two new records with (CONSOLIDATION_IND = 4) are matched, the record with the lowest ROWID_OBJECT wins.
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.