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.
[Oracle] "ORA-01792: maximum number of columns in a table or view is 1000" occurs - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • [Oracle] "ORA-01792: maximum number of columns in a table or view is 1000" occurs
KB0647718

[Oracle] "ORA-01792: maximum number of columns in a table or view is 1000" occurs


37654 Views Last updated : Mar 9, 2024 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Description

In some cases, Oracle queries may result in the following error:
[Oracle]  "ORA-01792: maximum number of columns in a table or view is 1000"

This can happen on CMDB tables or other tables such as Task.

Steps to Reproduce

This error occurs on ALTER TABLE statements for large tables like CMDB, and sometimes on SELECT JOINs on Task (recursive from rm_story for example) even when the number of columns on the task did not exceed 1000 nor did the number of columns defined for output.

Workaround

Choose from one of the following workarounds:

  • Try to specify a view with fewer columns.
    For more information, see the documentation topic Specify a field to return.
  • Apply the fix supplied by Oracle.
    According to My Oracle Support, ORA-01792 is caused due to an unpublished bug. Oracle suggests to alter the query and/or view definitions to avoid the error. However, in cases where the SQL cannot be adjusted, you can disable the checking as follows:
    SQL> alter system set "_fix_control"='17376322:OFF';
    Alternatively, you can apply an interim patch (patch 19509982) to disable the error by default.
    References:
    • Bug 19509982 Disable raising of ORA-1792 by default (https://support.oracle.com/epmos/faces/DocumentDisplay?id=19509982.8)
    • Select Statement Throws ORA-01792 Error (https://support.oracle.com/epmos/faces/DocumentDisplay?id=1951689.1)

    After this change restart the instance.

    This fix has been available since about June 2017 and can be applied as a one-off patch.

  • October 2017 Patch Set Update and Bundle Patch Set updates that include this fix have been released. The Bundle Patch Set updates include optimizer fixes and are now Oracle's recommended patching method. However, they require uninstalling the Patch Set Update first before applying the Bundle Patch Set update.

Related Problem: PRB732366

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.