- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2019 01:56 PM
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!
Solved! Go to Solution.
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2019 08:05 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2019 03:44 PM
Curious. Is there actually an indicator with the SYS_ID its complaining about?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2019 07:15 AM
If there is, I can't find it in any of the instances.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2019 04:19 PM
Try running the Performance Analytics Diagnostics: https://docs.servicenow.com/bundle/madrid-performance-analytics-and-reporting/page/use/performance-a...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2019 07:15 AM
I did, but it just tells me to check the job log, and it just says that it can't find that SysID.