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

Riya25
Giga Contributor

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

 

1 ACCEPTED SOLUTION

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

26 REPLIES 26

Hello Vishwa,

I have already gone through these links but still i was not satisfied as ideally if the name is same then ci should be updated rather than being created that's why ask the Question.

 

Regards,

Riya

Azim Kazi
Giga Guru

Hi Riya ,

as you said you created identifier for serial number and newer CI coming with empty serial number so it is not finding match that is why its creating new CI

 

 

Regards,

Ajim

and all cmdb rules does not work for manual creation of CI

Riya25
Giga Contributor

Hello Ajim,

Thank you for the reply,

So since its a manual import so it will not go through all Identifier rules as in case of Discovery.

Since Serial number is empty it should check for name identifier atleast.

How can we solve this inorder to avoid the creation of duplicates in future.

 

Regards,

Riya

 

ok then you need to create one more identifier for name field but in that case if your organisation having same name of people so best way is you analyse one more field which can be unique and create identifier for that attribute