CMDBHealth Duplicate Job failing

[benjaminayo]

Hello,

I am looking to resolve duplicate/correctness scheduled jobs error. Status is incomplete when looking at the CMDB Health Metric Status.. 

Looking at the CMDB Health Processor Status, the CMDB_ci_hardware has been in "in progress" status.

Looking at the sys log, I found these two error messages below:
- CMDBHealth : DUPLICATE error : java.lang.NumberFormatException: For input dtring: "Null"
- CMDBHealth : DUPLICATE Error while processing batch : cmdb_ci_hardware Last processed id: Marking as incomplete and exiting: no thrown error
CMDBHealth : DUPLICATE

** UPDATE **

Still dealing with this, I found out someone imported into the alm_hardware table and CIs were created without going through the IRe thus causing the jobs to fail.. Im looking into trying to create a transform map with IRE scripted to run those through the IRE, I dont know if this is best practice or if anyone has dealth wth this before please adivse..
Please advise

[Kommineni]

Hi Benjamin,

The NumberFormatException: For input string: "Null" during the CMDB Health Duplicate job is commonly caused by one or more CIs in cmdb_ci_hardware having an empty/invalid Discovery source.

Please check cmdb_ci_hardware.LIST with:

Discovery source is empty

Correct those CI records with the proper Discovery Source, then rerun the CMDB Health Duplicate job.

After that, verify:

• cmdb_health_processor_status > cmdb_ci_hardware  should no longer remain In Progress
• cmdb_health_metric_status > Duplicate should complete successfully

I would not manually reset the health status records before fixing the bad CI data, otherwise the job will fail again.

Regards,
Shankar Kommineni

[benjaminayo]

Would selecting the discovery source manually work? Or would I have to run these records through the IRE first? it looks like they may have not ran through the IRE when I check the CMDB data score metric the "CIs Processed via IRE" matches the amount if CIs missing discovery sources...


the CIs missing discovery source attribute were originally on a staging table but was brought in via importing through hardware table, we created a transform map and integration hub to try and run them through but does not seem to fix the issue..

[Sandeep _]

Hi @benjaminayo 

This error usually indicates that the CMDB Health Duplicate job encountered invalid data while processing records in the cmdb_ci_hardware table. [servicenow.com], [hi.service-now.com]

Please review the Discovery Source field and look for blank, null, or invalid values, as these are a common cause of Duplicate job failures. [servicenow.com], [hi.service-now.com]

Also verify that the affected CIs have a valid sys_class_name, since invalid class values can cause the job to stop unexpectedly. [support.se...icenow.com]

After correcting any data issues, rerun the CMDB Health Duplicate job and check whether the processor status changes from In Progress to Complete. [servicenow.com], [servicenow.com]

Reference- https://www.servicenow.com/community/cmdb-forum/cmdbhealth-duplicate-job-failing/m-p/3593181 [servicenow.com]