CMDB Health jobs not working as expected in domain separated environment - Support and Troubleshooting

CMDB Health jobs not working as expected in domain separated environment Issue CMDB Health jobs not working as expected in domain separated environment

For example, for domain separated environment, you will observed even though the CMDB health scheduled jobs (Completeness/Correctness/Compliance) are running everyday, you wont see desired CI's getting updated in 'cmdb_health_result' table

Cause This could happen if there are orphan domain records present and some CI's are referencing to the orphan domain (non existing) records in 'cmdb_ci' table. For this you can group records in 'cmdb_ci' table with domain and see if any group is referencing to non existing domain.

Resolution Make sure records in 'cmdb_ci' has valid domain, if not remove CI records or change its domain to valid entry Make sure, 'Ci Health Availability' is set to true for metrics in 'cmdb_health_metric' table Make sure, records in 'cmdb_health_metric_status' and 'cmdb_health_metric_pref' are active (These are domain specific records) After above points taken care make sure, there no records left in below table except status complete in 'cmdb_health_processor_status' table. If there are any, delete them all. Once done, execute CMDB health job's and see if this time the CMDB health result table 'cmdb_health_result' is populating as expected Also refer below few KB's which might help troubleshooting this issue; https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0725777

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-management/concept/cmdb-health-domain-separation.html

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0859805