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
- 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.
- Upgrade the instance to Geneva.
- 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