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.
Table alters via update set sometimes do not invalidate cache correctly on other nodes - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Table alters via update set sometimes do not invalidate cache correctly on other nodes
KB0695145

Table alters via update set sometimes do not invalidate cache correctly on other nodes


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

Description

Table alters via update set sometimes do not invalidate cache correctly on other nodes. The table descriptor cache for the affected table must be invalidated manually in order to correct the issue. If the alter is a column creation, this can result in the column not being visible on some nodes. If the alter is a column drop, this can cause SQL syntax errors on some nodes such as the one below:

"Syntax Error or Access Rule Violation detected by database (Unknown column 'task0.u_sla_response' in 'field list')"

Steps to Reproduce

Any table-altering change committed via update set is susceptible to this issue. It seems to be correlated with user activity on other nodes at the time of the commit, but this is not confirmed.

Workaround

Flush the table descriptor cache for the affected table by running this script from the Scripts - Background module:

GlideTableManager.invalidateTable('table_name');
GlideCacheManager.flushTable('table_name');

NOTE: As a last resort, you can use gs.invalidateCache(); but this will degrade performance on the instance.


Related Problem: PRB1294784

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.