Having an issue with the PA daily data collection job.

Joel Pomales1
Tera Contributor

Hello all.

We recently upgraded our sub-production environments to London. We noticed that the PA incident daily data collection job is errorring out. The error happens at the beginning of the run, and the job completes. We can't find the SysID referenced in the log anywhere. 

There is an entry on the indicators related to the job that appears as (empty). However, the SysID of that entry does not correspond to that entry.

Weirdness!

1 ACCEPTED SOLUTION

Have you validated that the Incidators table has no Indicator for that sys_id?  
Keep in mind that when you're looking at the "indicator" records at the bottom of a job, you're not actually looking at indicators.  You're looking at an m2m record linking indicators to jobs.  That might explain the "this sys_id isn't that" weirdness you describe.


Check your deleted records to see if you've got any deleted indicators.  Sounds like maybe one was deleted but the delete didn't cascade to the job-indicators m2m table.

View solution in original post

8 REPLIES 8

Uncle Rob
Kilo Patron

Curious.  Is there actually an indicator with the SYS_ID its complaining about?

If there is, I can't find it in any of the instances.

Adam Stout
ServiceNow Employee
ServiceNow Employee

I did, but it just tells me to check the job log, and it just says that it can't find that SysID.