Yes, this is a duplicate of CONF-32139, but it is because that issue was marked as Resolved because there was a desire not to delete pre-existing indexes.

      I think the proper resolution here is to do some checking in the upgrade task to determine if the index already exists and if so, use that index versus creating a new index. I know that SailPoint did this when we had many hundreds of clients running Oracle who added indexes for performance reasons through the Statistics and Query Analyser tools that improved performance in our application. This made the upgrade tasks run smoothly to finish without upsetting the clients who had already added indexes by halting their upgrade tasks.

      I would like to have this issue revisited as our largest clients are running Oracle backends and will see this issue in their environments. If we checked for the existence of an index on the table and column that we are about to index and then did not do so if it already exists, then the upgrade experience would be smoother overall.

            [CONFSERVER-36652] Oracle Upgrade Fails due to pre-existing indexes

            George Varghese made changes -
            QA Demo Status New: Not Needed [ 14332 ]
            QA Kickoff Status New: Not Needed [ 14236 ]
            Resolution New: Low Engagement [ 10300 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            George Varghese made changes -
            Labels Original: affects-server oracle pse-request sc upgrade upgrade-manager upgrade_task New: affects-server cleanup-seos-fy25 oracle pse-request sc upgrade upgrade-manager upgrade_task
            SET Analytics Bot made changes -
            UIS Original: 3 New: 4
            SET Analytics Bot made changes -
            UIS Original: 4 New: 3
            Conny Postma made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 95442 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 4
            SET Analytics Bot made changes -
            UIS Original: 4 New: 1
            SET Analytics Bot made changes -
            UIS Original: 3 New: 4
            SET Analytics Bot made changes -
            UIS Original: 4 New: 3
            SET Analytics Bot made changes -
            UIS Original: 7 New: 4

              Unassigned Unassigned
              ctalk chucktalk (Inactive)
              Affected customers:
              6 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: