Corrupted Oracle Index Breaks JIRA Upgrade
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When the customer upgrades their JIRA instance that is connected to Oracle DB, they would get an error letting them know JIRA failed and looking at their log, they should see the following errors in atlassian-jira.log
1
2
3
4
5
6
(SQL Exception while executing the following:INSERT INTO propertytext (ID, propertyvalue) VALUES (?, ?) (ORA-01502: index 'JIRA.PK_PROPERTYTEXT' or partition of such index is in unusable state
))
Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation
Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition
The error seems not to be related to the KB I sent to you earlier as it seems that this is related to a corrupted index within your oracle database as explained here
Cause
An index partition is corrupted in his JIRA Database, affected indexes would be mentioned in error thrown in the log.
Workaround
Option 1
Create a new Oracle Database(this fixes the corrupted index)
Install new JIRA you want to migrate to.
Connect it to JIRA.
When JIRA is Started, proceed to restore your old backup you had before you perform the upgrade.
Option 2
Follow the steps mentioned in this document to recreate the affected indexes(note that the affected ones are listed in atlassian-jira.log) in this case
ORA-01502: index 'JIRA.PK_PROPERTYTEXT'
ORA-01502: index 'JIRA.PK_JIRAWORKFLOWS'
Once done, restart JIRA with the corrected database and reattempt the upload.
Was this helpful?