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.
New cmdb_ci table hierarchy causes loss of composite database indexes from the new cmdb table, potentially impacting performance - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • New cmdb_ci table hierarchy causes loss of composite database indexes from the new cmdb table, potentially impacting performance
KB0596386

New cmdb_ci table hierarchy causes loss of composite database indexes from the new cmdb table, potentially impacting performance


880 Views Last updated : Apr 8, 2025 public Copy Permalink
KB Summary by Now Assist

Description

The cmdb_ci table hierarchy has been re-parented in the Geneva release with a new parent [cmdb]). Therefore, if an instance that has been upgraded to Geneva had custom indexes on the cmdb_ci table involving custom columns or columns that were promoted to the base table ([cmdb]), these indexes might not exist after the upgrade and performance is affected.

Steps to Reproduce

  1. On a pre-Geneva instance, create custom indexes on the cmdb_ci table involving custom columns or columns that will end up being promoted to the base table after the upgrade.
  2. Upgrade the instance to Geneva.
  3. Check indexes for the cmdb table.

Workaround

Review the indexes that existed prior to the upgrade, and then use the Index Creator form in the Tables & Columns module to manually re-create the indexes that were lost.


Related Problem: PRB671489

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.