Atlassian Bitbucket v8.19.3 Database upgrade is failling- active-objects tables

[Karthick Vijayakumar]

2025-07-10 11:36:57,676 WARN [spring-startup] c.a.s.i.p.s.OsgiBundledPathScanner Cannot scan directory /extension/build-status/ in bundle com.atlassian.bitbucket.server.bitbucket-frontend; it does not exist
2025-07-10 11:36:57,842 INFO [active-objects-init-0] c.a.b.i.d.dao.v1.MigrateToV1Task Starting to migrate default reviewers model data
2025-07-10 11:36:57,935 ERROR [active-objects-init-0] net.java.ao.sql Exception executing SQL update <ALTER TABLE "AO_9DEC2A_PR_CONDITION" ADD COLUMN "REPOSITORY_ID" INTEGER NOT NULL>
org.postgresql.util.PSQLException: ERROR: column "REPOSITORY_ID" of relation "AO_9DEC2A_PR_CONDITION" contains null values
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713)

[Fabio Racobaldo _Catworkx_]

Hi @Karthick Vijayakumar and welcome,

before going ahead with the upgrade please verify that table "AO_9DEC2A_PR_CONDITION" has not NULL values for column "REPOSITORY_ID".

If so try first to reindex your bitbucket instance (https://support.atlassian.com/bitbucket-data-center/kb/rebuild-the-search-server-indexes-for-bitbucket-data-center/) 

(Recommended) Resolution #1 - trigger a reindex

The Bitbucket Server REST API provides a way to restart indexing by making an HTTP request. This can be done when running a Bitbucket instance using the following curl command to make a POST to the /rest/indexing/latest/sync REST endpoint:

curl -u <admin-user> -X POST -H 'Content-Type: application/json' -H 'Accept: application/json' <bitbucket-url>/rest/indexing/latest/sync

This will trigger a re-index of all repositories. Bitbucket will be available with all functionality other than the search of unindexed portions of your code. The time it takes to index depends on how much indexable content you have. This will be the amount of code contained in files under 512 KB.

To check the Search Indexing status:

ℹ️ The Search reindexing or indexing triggered is run on a single Bitbucket node. Hence, checking it directly using the Bitbucket base URL will not yield the correct results, as the request could land on any of the Bitbucket nodes randomly. So, it is advised to check the reindexing status directly on the Bitbucket node's IP using the HTTP port number to find the indexing status. If there are multiple nodes, this must be checked against each node to determine which one is running the indexing.

curl -u <admin-user> -X GET -H 'Content-Type: application/json' -H 'Accept: application/json' <bitbucket-node-ip>:port_no/rest/indexing/latest/status

My suggestion is to test upgrade process in a preprod environment first.

Hope this helps,

Fabio