Jira Re-index not completing after restoring an XML Backup using Oracle Database
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
Summary
After restoring a Jira XML backup file, using an Oracle database, Jira is unable to re-index properly, along with several database-related errors in the logs, as in the example below:
1
2
3
4
5
6
7
8
9
10
11
com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:Oracle
- version:Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.14.0.0.0
- minor version:0
- major version:19
Driver:
- name:Oracle JDBC driver
- version:19.3.0.0.0
java.sql.SQLIntegrityConstraintViolationException: ORA-01400: cannot insert NULL into ("JIRA"."AO_4789DD_HEALTH_CHECK_STATUS"."ID")Environment
Jira 8+
Oracle Database
Diagnosis
This problem can be caused by several different reasons, and you should first verify the article to make sure that all triggers have been enabled correctly:
Also, make sure that permissions for the user you are using in Jira to connect to the database has the required permissions to use the triggers, as detailed below:
Additionally, confirm that Advanced Compression is turned OFF.
Compare the number of triggers from both databases, using the query below:
1
select * from user_triggers where TABLE_NAME like '%AO_%';Cause
If you notice a difference between those numbers, then you should proceed and recreate the triggers. They have not been imported due to incorrect database user permissions when the XML backup was restored.
Solution
Recreate all missing triggers manually.
Was this helpful?