If Serial Number is empty and name is same then why duplicates are getting created

Riya25 · ‎05-07-2020

Hello Experts,

Recently we have a issue in which duplicate CI's are getting created having the Serial Number Empty but Name is same.

As per the identification when Serial Number is empty it should have checked for the Name Identifier then why duplicates are being created instead of updating the same record?

Also,after discovering the duplicates Class is different than the class of existing CI and IP address is same also in the Created By field name of user is occurring.

Please help!!

Regards,

Riya

Azim Kazi · ‎05-11-2020

Hi Riya,

Can you please help which field we should consider other than serial number ,name to make a new Identifier rule especially for server table.

👉 You can use IP address attribute to create record uniquely or you can make asset tag as well if server is physical.

And also to delete the duplicates we should run the background script on individual table or base table (cmdb_ci)

👉 I suggest you to delete by individual class and check if it working fine or not it won't take much time.

whether deleting will automatically delete the their respective Relationships or not ?

👉 Yes,it will delete relationship as well.

Regards,

Ajim.

View solution in original post

Jaspal Singh · ‎05-07-2020

Hi Riya,

How are CIs created? Is it via data import or via discovery?

If it uses data import then you need to make sure the datasource has field correctly coalesced so as to avoid duplicates.

Riya25 · ‎05-07-2020

Hello Jaspal,

Thank you for the reply.

But van you please tell me how to differentiate between manually Imported CI and CI created through discovery.

Regards,

Riya

Jaspal Singh · ‎05-07-2020

Simple way would be to check the created_by name. It should be non system account for the import done manually via datasource.

Riya25 · ‎05-07-2020

Hello Jaspal,

I have checked that in the duplicate record created by contains the name of the user so that one is a manual Import.

And if so in order to avoid this we need to to carefully use the Coalense field right so that duplicate cannot be created.

Regards,

Riya