-
Bug
-
Resolution: Low Engagement
-
Medium
-
None
-
5.7
-
19
-
Severity 2 - Major
-
4
-
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.
- mentioned in
-
![[Atlassian Documentation] Page](/images/icons/generic_link_16.png "[Atlassian Documentation] Page")
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page
No Confluence page found with the given URL.
-
Page Loading...
-
[CONFSERVER-36652] Oracle Upgrade Fails due to pre-existing indexes
| 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 ] |
| 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 |
| UIS | Original: 3 | New: 4 |
| UIS | Original: 4 | New: 3 |
| Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 95442 ] |
| UIS | Original: 1 | New: 4 |
| UIS | Original: 4 | New: 1 |
| UIS | Original: 3 | New: 4 |
| UIS | Original: 4 | New: 3 |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center