Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Error "Error collecting for <integer> java.lang.IllegalStateException: Sparse storage format has one field, sys_id" in Performance Analytics Data Collection job log - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Error "Error collecting for <integer> java.lang.IllegalStateException: Sparse storage format has one field, sys_id" in Performance Analytics Data Collection job log
KB0550063

Error "Error collecting for <integer> java.lang.IllegalStateException: Sparse storage format has one field, sys_id" in Performance Analytics Data Collection job log


5448 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

The following error can appear in the Performance Analytics job logs:
Sparse storage format has one field, sys_id 

Example:

Error collecting for 20180508 java.lang.IllegalStateException: Sparse storage format has one field, sys_id
at com.glide.db.meta.SparseStorage.getValue(SparseStorage.java:70)
at com.snc.pa.dc.Row.getValue(Row.java:164)
at com.snc.pa.dc.DataCollector.map(DataCollector.java:565)
at com.snc.pa.dc.DataCollector.collect(DataCollector.java:355)

Release

Any release

Cause

This error can be caused by:

  • the fact table of the breakdown assigned to an indicator being different from the fact table from the indicator
  • the script used in an indicator referring to a table column that does not exist
  • an indicator using an aggregate combined with a column that does not exist

Resolution

The instance localhost log will just show a stack dump, but nothing else, there is no trace of what table and field is attempted to be read. The following steps may be of help before creating an incident for SN support:

  1. View the job log in the instance localhost
  2. Search for the error message "java.lang.IllegalStateException: Sparse storage format has one field, sys_id"
  3. Just after the error message, you should see a line with the field and table that can not be found "Syntax Error or Access Rule Violation detected by database (Unknown column '<table>.<field>' in 'field list')"
  4. Identify the first preceding row where the message contains "Processing Indicator Source ..."
  5. Use the indicator source mentioned, to search for associated automated indicators
  6. For each indicator verify the breakdowns and scripts used

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.