we have a running integration between UCMDB 10.10 and SM 9.31 and are replicating a lot of CIs to SM.
For some CIs we get "dublicate key errors" and the CIs are not replicated. The reason is that the UCMDB Id for nodes do change (after in UCMDB the CI gets deleted for any reason and recreated again with the same hostname).
In SM the (out-of-the-box) reconciliation key seems to be the UCMDB Id.
Are there recommendations to deal with this issue? Is a change in the SM reconciliation (to logical.name) recommendet?
On the other hand we can never 100% prevent CIs from beeing deleted and recreated (change of UCMDB Id).
Thanks for your help,
Re: SM Integration
SM R&D are the owners of this integration. Probably it will be best if you contact them regarding the SM reconciliation rule change. If there are just few CIs in SM with this issue I believe you can workaround the problem if you delete the ucmdb id for these CIs in SM and then rerun the push job.
However, from uCMDB side we can investigate why these CIs are deleted. They can be deleted by aging / probe automatic deletion mechanism or they are merged. To investigate these we need probe and server logs. Best way is to investigate this through a support ticket.