Symptoms

An incorrect procedure to upgrade Bitbucket Server results in:

The target database contains tables which will clash with Bitbucket Server's tables. For information about how to clean up your databases for use with Bitbucket Server, please refer to the Bitbucket Server documentation.
	com.atlassian.bitbucket.internal.migration.DefaultMigrationService.validateDataSource(DefaultMigrationService.java:1008)
	com.atlassian.bitbucket.internal.migration.DefaultMigrationService.validateConfiguration(DefaultMigrationService.java:257)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)       

Cause

Customers running into this issue are trying to upgrade Bitbucket Server using an incorrect procedure for upgrading their instances.

Bitbucket Server upgrade's philosophy is very simple:

• Download and install the new release
• Point the new binaries to your current BITBUCKET_HOME

• Bitbucket Server will perform the upgrade automatically for you.

We suggest you follow the Bitbucket Server upgrade guide and use the installer to Upgrade your instance in order to accomplish the steps above.

We've seen 2 scenarios where this occurs:

1- Incorrectly setting the new release to point to an empty BITBUCKET_HOME 

If you point your instance to an empty BITBUCKET_HOME , Bitbucket Server will act as if this is a first install. An attempt to have Bitbucket Server linked to your current database will result in the error above.

2- Incorrectly setting the new release to point to an empty BITBUCKET_HOME and trying to migrate databases using the "Migrate Database" wizard tool.

If you point your instance to an empty BITBUCKET_HOME , Bitbucket Server will act as if this is a first install. An attempt to migrate databases is incorrect and will not upgrade your instance. Bitbucket Server database has to be in sync with BITBUCKET_HOME.

Related Content

Answers: Bitbucket Server Upgrade 2.0.3 -> 2.1 - database table clash?

Resolution

Refer to Bitbucket Server upgrade guide and execute all its steps. Ensure that your new installation is pointing to the correct value of your current BITBUCKET_HOME.