Discovery Pattern Error - Found duplicate records in table [cmdb_ci_hardware] using fields [serial_number]

Sanil
Kilo Contributor

Hi,

While discovery windows server and facing below error.

Found duplicate records in table [cmdb_ci_hardware] using fields [serial_number],Too many other errors,Abandoning processing payload item

I have tried deleting serial numbers which were duplicates on cmdb_ci_hardware table. Also tried deleting entre ci and re-discovered the CI again.

But no luck, can any one suggest solution to this problem.

Thanks,

Sanil Chavan 

 

2 REPLIES 2

Anshu_Anand_
Kilo Sage
Kilo Sage

Have you checked serial number table cmdb_serial_number.

when discovery tries to discover, it first go by identification rule.

1. serial_number and type matches, it updates the record, not found, goes to next identifier and so on until it finds a match. else create a new CI

2. In your case you are deleting the serial number for maybe bios, but discovery is matching baseboard type.

same maybe IP is same for 2 servers. a retired ci could also be discovering.

Best way in order to get rid of the duplicate CI, use remediation feature from cmdb health dashboard duplicate scorecard.

If you want to delete anyway, you have to delete the duplicate CI, its relationships, its serial records in serial number table.

Then try to discover the CI.

Hope its helpful

 

Regards,
Anshu

RGreene
Tera Expert

I have seen this issue also. Some times you will see the at top of the record that it is a duplicate. In that case you should go through the deduplication process, it will handle related and relationship record migration. 

If it is not flagged as a duplicate, I have found these to be stub records/incomplete records, these can be deleted.  But you need to see what is the best record to keep.  We have noticed that the stub record was created and discovered only one or two time and then the original record is used again.

My thoughts are the IRE get confused or works incorrectly when the instance is under stress(High user load, Promotion to production activities, Patching, Upgrades)  I say this because we see a higher number of these duplicates during the stress periods.