-
-
2. Re: MDM Matching Issue.
Hi Anuvinda,
Yes CI=1 is matching with CI =4 of non distinct source system.
Thanks,
-
3. Re: MDM Matching Issue.
You may want to confirm whether you have AutoRules only check enabled for the Distinct Source system -
-
4. Re: MDM Matching Issue.
Apart from checking the AutoRules only check that Kunal suggested above, you can also try replicating this issue (using a handful of records) with cmx.server.datalayer.cleanse.working_files=KEEP set in cmxcleanse.properties file (this change needs a server restart). This will retain the temporary files used during matching and you can check through these files if the CI=1 record matched with both CI=4 (from non-distinct sytem) and CI=4 (from distinct system), and if the match for CI=1 <---> CI=4 (from distinct system) was removed because of BMG.
-
5. Re: MDM Matching Issue.
Hi Kunal,
We don't have Auto Rules Only checked, because we don't want Distinct source system to match against itself. Only Distinct feature is enabled,
We are having two source system one is normal which has highest trust score and the second one which is marked as distinct is having lower trust score. So the problem occur when Normal source system is golden record(CI=1) and new distinct source system comes to base object. Now the CI =1 golden is not participating in the match with this distinct source system with CI = 4 and as a result this new record is also becoming golden record.
Thanks,
-
6. Re: MDM Matching Issue.
Hi Anuvinda,
according to your scenario ,
" if the CI=1 record matched with both CI=4 (from non-distinct sytem) and CI=4 (from distinct system), and if the match for CI=1 <---> CI=4 (from distinct system) was removed because of BMG." this is correct
What if we only have one CI = 1 record(from non-distinct system) and one CI =4 ( from distinct system) ,
here this CI=1(from non-distinct system) is not participating with this CI=4( from distinct system).
Thanks,
-
7. Re: MDM Matching Issue.
Hi,
What is the best practice for BMG indicator, can we make it '0'??
Thanks,
-
9. Re: MDM Matching Issue.
I don’t see a reason why the CI=1 record doesn’t match with new incoming record.
Yes you can try disabling the BMG in the C_REPOS_TABLE for your BO for testing reasons.
Once you found the root cause, you can act accordingly and revert BMG back to normal
Sathiesh M | Infa GCS-MDM
-
-
10. Re: MDM Matching Issue.
Hi Sathiesh,
CI=1 record of normal source system doesn’t match with new incoming record of Distinct source only, it is coming in match if new incoming record is from normal source system.
And I tested with making BMG = 0 for only that particular table name, but this is also did not work still same issue.
Thanks,
-
11. Re: MDM Matching Issue.
Hi Aziz,
You may want to raise a ticket with Informatica Support and share sample data for these 3 records: CI=1, CI=4 from non-distinct source, CI=4 from distinct source, along with match rules configured, as well as the cleanse logs when you replicate this scenario. We may have to take a look at these and possibly replicate this issue in-house.
Thanks.
-
12. Re: MDM Matching Issue.
Hi Anuvinda,
Ok I will have a word my team and raise a ticket regarding this issue,
Thank you.
