Problem Definition

Bamboo has a repeatable upgrade task (60204) that creates foreign key indices for DBMS that don't do this by default.

Two issues with this upgrade task:

1. It does not trigger on the first startup, but instead needs a restart
2. It does not run on every startup, but only once per version
3. It tries to create an index even if a functionally identical index already exists (affects AO_ tables) -> fixed under https://jira.atlassian.com/browse/BAM-25899

Suggested Solution

1. Allow this Task to run on every startup, similar to the schema check process

Why this is important

The lack of any indices in the Bamboo database can cause a significant degradation in performance. In extreme cases, queries that may take over 10 hours without indices run in a seconds once they are added and refreshed.

Workaround

There is no official workaround, but please contact support at https://support.atlassian.com/contact for assistance.