<(CM) Support tip>Schema upgrade fails due to error of failing to create existing index
Incident description :
Schema upgrade fails due to an error of failing to recreate existing index.
Root cause to the issue is that the DB index on DB table was given a different name and schema upgrade couldn't drop that index with assigned name (not the Index name used original by HPE CM/RM), this creates the problem at later step when Schema upgrade attempts to recreate index, which will fail and stalls schema upgrade.
DBA should consider getting indexes on HPE CM/RM tables dropped before running schema upgrade.
Or Schema Repair function in HPE CM/RM Enterprise studio can be utilized to get the CM/RM indexes recreated before the upgrade.
Please note that using schema repair getting index recreated will also remove any custom indexes, and DBA should review the existing indexes on HPE CM/RM tables before doing this, and if the decision of running schema repair to get the indexes recreated is made, the DBA may need to recreate those custom indexes manually after schema upgrade is done (if necessary).
Please back up the database before making any change, and test the steps in a testing environment against a duplicated DB before auctioning against PROD DB.