Unique constraint (BAMBOO.SYS_C0011413) violated after Bamboo 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
Summary
Unique constraint error is showing up in the Bamboo logs right after upgrading Bamboo.
Environment
Bamboo 7.2.3
Diagnosis
The following messages can be found in the atlassian-bamboo.log file:
1
2
3
4
5
ORA-00001: unique constraint (BAMBOO.VCSPULLREQ_KEYTARGETREPO_IDX) violated
ORA-00001: unique constraint (BAMBOO.SYS_C0011414) violated
ORA-00001: unique constraint (BAMBOO.SYS_C0011412) violated
ORA-00001: unique constraint (BAMBOO.SYS_C0011413) violated
ORA-00001: unique constraint (BAMBOO.SYS_C0011434) violatedCause
This can be caused due to some database corruption.
Solution
Stop Bamboo
Create a database backup
Run the commands below against Bamboo database:
1 2 3 4 5ALTER INDEX BAMBOO.VCSPULLREQ_KEYTARGETREPO_IDX REBUILD; ALTER INDEX BAMBOO.SYS_C0011414 REBUILD; ALTER INDEX BAMBOO.SYS_C0011412 REBUILD; ALTER INDEX BAMBOO.SYS_C0011413 REBUILD; ALTER INDEX BAMBOO.SYS_C0011434 REBUILD;Start Bamboo back
Was this helpful?