CMDB Health - Orphan Remediation

[Tom104]

Hi All,

I'm looking into remediating several health issues with our CMDB.

One significant issue is the number of Orphan Records on the estate, currently circa 50k+

Will using remediation rules therefore generate 50k tasks, one per CI, or just one task?
I've tried to report on this in list view, but can't find any way to generate the list of CIs to allow manual deletion. 

Failing this, is there any suggestion as to how I can bulk delete the Orphan CIs, we're only targeting the application class currently?

Current Metric is "Application" has no Runs "On:Runs" relationship.

Thanks

[Mark Manders]

The task creation is meant to be assigned to someone to decide 'hey, this application doesn't run on anything, is it missing a relationship, or is it really old and aren't we using it anymore' and then take appropriate actions.

With 50K+ applications that don't have a 'runs on' relationship, I highly doubt all of them are really ready for deletion. It could very well be that a server was decommissioned and someone forgot to update the new server the application is running on.

But if it really is just a mess and you need to get rid of those applications, you could query to the application table, validate if they have such a relationship and if not, delete them. A backgrounds script could do this, but I think you will be deleting too much.

[Tom104]

Thanks Mark, this is absolutely just a case of redundant data. The Cascade rule wasn't enforced historically, a lot of internal customisation which stopped Child CIs from being deleted, as such they're now orphans. We've never had Application ownership, just the one man band that is me trying to keep it from falling over.

[Sandeep90]

You can get the list of CIs data directly from cmdb_health_result table and use multidelete to delete those records.  Please cross check you got correct results before deleting them. 

[Tom104]

Hi Sandeep,

Sadly it doesn't look like multi-delete is available from that table. You have to access each individual CI and perform the deletion.

Secondly, I would assume that even if this worked that this simply deletes the Health Result, as opposed to the configuration item itself.