Active Objects tables created without Indexes or Identity Columns

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

Problem

After a new installation or database restore, you may receive errors such as the following in the atlassian-bamboo.log

1 2 3 java.sql.SQLException: 'pk_AO_7A45FB_AOTRACKING_ENTRY_TRACKING_ID' is not a constraint. java.sql.SQLException: 'pk_AO_F36021_SONAR_SERVER_ENTITY_ID' is not a constraint. java.sql.SQLException: 'pk_AO_88263F_HEALTH_CHECK_STATUS_ID' is not a constraint.

Diagnosis

Environment

  • MS SQL Server database

  • jTDS driver

Cause

Root cause is currently undefined, but the tables were not created with primary key columns.

Solution

Resolution

Since these tables are created on Bamboo startup, please:

  1. Stop Bamboo

  2. Backup your Bamboo database

  3. Drop all Active Objects tables, which start with AO_, eg:

    • AO_7A45FB_AOTRACKING_ENTRY

    • AO_7A45FB_AOTRACKING_RESULT

    • AO_7A45FB_AOTRACKING_USER

  4. Start Bamboo

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.