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

Step 10. Test the Match Rules

Step 10. Test the Match Rules

To test the match rules, run the match job and review the results.
You can test the match rules on a sample data set that is representative of the larger data set. To test the match rules, run the match job on the sample, representative data set. After the match job completes, review the match results.
You can view the match results in the C_PARTY_MTCH match table that is associated with the Party base object. Also, you can view the match results through Merge Manager in the Hub Console, and through the Potential Matches option in Informatica Data Director. Review the matched records to verify their accuracy.
The C_PARTY_MTCH match table shows important columns that contain the sample match result.
ROWID_OBJECT
ROWID_OBJECT_MATCHED
ROWID_MATCH_RULE
AUTOMERGE_IND
1191
1019
SVR1.JJ4J
0
1191
1419
SVR1.JJ4J
0
1154
1106
SVR1.JJ4E
1
1642
1072
SVR1.JJ4E
1
The ROWID_OBJECT column contains the row ID of the records that are matched to the records with row ID in the ROWID_OBJECT_MATCHED column.
The ROWID_MATCH_RULE column contains the row ID of the match rules that you create. The match rules are in the C_REPOS_MATCH_RULE table in the repository. SVR1.JJ4J is the row ID of the match rule with the Resident match purpose and a loose match level. SVR1.JJ4E is the row ID of the match rule with the Resident match purpose and a typical match level.
The example shows that the record for William De Haan that has row ID 1191 has two matches. The record matches the individual with the row ID 1019, Will R De Haan, and the individual with the row ID 1419, Bill Roger De Haan. The matches are based on the name and address columns and are similar but need to be reviewed by a data steward before the merge. Both the matches of the record for William De Haan are queued for manual merge.
The match table shows that the record for Rachel Arsen that has row ID 1154 matches another record for Rachel Arsen that has row ID 1106. Both the records for Rachel Arsen have addresses in the Address base object that are similar and can be safely queued for automerge.
The following table shows the names of some individuals whose records were matched to other similar records:
Display Name
Display Name Matched
WILLIAM DE HAAN
WILL R DE HAAN
WILLIAM DE HAAN
BILL ROGER DE HAAN
RACHEL ARSEN
RACHEL ARSEN
AHMED RAUF
AHMED RAUF
The match result appears correct in the example. You can use the match rules that you configured for the larger match job.
To view any issues that might occur during the match job, review the
cmxserver.log
file located in the following directory:
On UNIX.
<infamdm_install_directory>/hub/server/logs
On Windows.
<infamdm_install_directory>\hub\server\logs
Timeouts can occur because of match properties such as the number of rows for each match job batch cycle. You can change the properties in the
Properties
tab of the
Match/Merge Setup
page.
To check the progress of the match job and to get summary statics, review the Process Server log.
The Process Server log,
cmxserver.log
, is in the following directory:
On UNIX.
<Process Server installation directory>/hub/cleanse/logs
On Windows.
<Process Server installation directory>\hub\cleanse\logs

0 COMMENTS

We’d like to hear from you!