Duplicate records keep getting created by the system in Asset table

[rin1]

Hi Experts,

Duplicate records getting created by the system very often in the Asset table. I have checked the transform maps, only sys_id is made Colaesce. Any idea why these duplicates getting created. Its really a stress to maintain Asset table.

Thanks,

Rini

[Scott Halverso1]

Troubleshooting the root cause of the duplicates is critical.  Any and all discovery tools should be using the identification and reconcilation engine.  By using the Service Graph connectors it guarantees that.  You've also got duplicate CIs.  With the Rome release I highly recommend turning on the multisource CMDB property when you have multiple sources of truth feed the CMDB.

If your root cause analysis determines it's not coming in from the CMDB side of the house, then look at asset direct imports which doesn't have an IRE engine wrapping the ALM tables.  

[rin1]

Hi scott,

When I further investigated, the child tables (Alm_asset & alm_hardware) had 2 records with same asset tag ‘LT10022112’ and I deleted the duplicate records. The record which I deleted earlier was removed from the parent table ‘cmdb_ci_hardware’. During next import system checked for the record in parent table, it couldn’t find it and so created a new record I believe.

Found one more thing, duplicate records are getting added in child tables, not in parent tables. So I have decided to compare both parent & child table delete the irrelevant record. Also update the coalesce field of Asset tag to true in the scheduled imports as a 2nd level filter. And see if it works.

Thanks,

Rini

[CMDB Whisperer]

Coalescing on sys_id isn't going to do you any good.  It is as good as not coalescing on anything.  You should be coalescing on serial number or asset tag, depending on what data is likely to exist in your data source.

[rin1]

Hi Paul,

When I further investigated, the child tables (Alm_asset & alm_hardware) had 2 records with same asset tag ‘LT10022112’ and I deleted the duplicate records. The record which I deleted earlier was removed from the parent table ‘cmdb_ci_hardware’. During next import system checked for the record in parent table, it couldn’t find it and so created a new record I believe.

Found one more thing, duplicate records are getting added in child tables, not in parent tables. So I have decided to compare both parent & child table delete the irrelevant record. Also update the coalesce field of Asset tag to true in the scheduled imports as a 2nd level filter. And see if it works.

Thanks,

Rini

[Mark Guldhammer]

How many data sources are you using?

I have had many struggles with 2 sources, which our vendor claimed where in sync. This resulted in duplicates, overwrites and tons of corrupt records.