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.


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

Seen In

Helsinki Patch 2

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-02-28 19:15:45