How to fix CI references on incident/change after CI recreated?

[Mihir YSSS]

We have a need to do full reboot of CMDB and reconfigure data sources. But there are some CIs which were referenced in incidents and change. After reconfiguration, same CIs will come to SN but with different sys_id. What will happen to CIs that were referenced in incident/change also how to map new CIs after reconfiguration?

[Dr Atul G- LNG]

Hi @Mihir YSSS 

Reboot CMDB is big task and that will spoil not only Modules but also reports / dashboard and other logics as well.

Avoid any changes in CI which are in good format, if required udpate the information but dont create fresh.

If you still want ful reboot, then those CI will be come in blue colour on records, means those not exits now and you need to manually update those record.

Try this Dev instance with limited CI so see the impact and risk analysis.

[Mihir YSSS]

Can we write any scripts with following steps:

1. Script to identify what are the CIs that were referenced in incident/problem. 
2. after reboot, identify the CIs with the same name and update them in incident/problem. 

Is this approach works?

[Dr Atul G- LNG]

Hi @Mihir YSSS 

I am sure there is way to do scripting,  but I am not pro/ coder in SN also I am think, this will effect all records, means closed records as well, will you/ client agree to ignored close records if ci has been changed or show as blue.

Also we can see linked records on each CI and we can create a report for same. Again for safe side, try this in lower env or in PDI first.