Stash Upgrade Fails with: tables whose names collide with Stash
Symptoms
An incorrect procedure to upgrade Stash results in:
The target database contains tables which will clash with Stash's tables. For information about how to clean up your databases for use with Stash, please refer to the Stash documentation.
com.atlassian.stash.internal.migration.DefaultMigrationService.validateDataSource(DefaultMigrationService.java:1008)
com.atlassian.stash.internal.migration.DefaultMigrationService.validateConfiguration(DefaultMigrationService.java:257)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Cause
Customers running into this issue are trying to upgrade Stash using an incorrect procedure for upgrading their instances.
Stash upgrade's philosophy is very simple:
- Download and install the new release
- Point the new binaries to your current
STASH_HOME Stash will perform the upgrade automatically for you.
We suggest you follow the Stash 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 STASH_HOME
If you point your instance to an empty STASH_HOME , Stash will act as if this is a first install. An attempt to have Stash linked to your current database will result in the error above.
2- Incorrectly setting the new release to point to an empty STASH_HOME and trying to migrate databases using the "Migrate Database" wizard tool.
If you point your instance to an empty STASH_HOME , Stash will act as if this is a first install. An attempt to migrate databases is incorrect and will not upgrade your instance. Stash database has to be in sync with STASH_HOME.
Related Content
Answers: Stash Upgrade 2.0.3 -> 2.1 - database table clash?
Resolution
Refer to Stash upgrade guide and execute all its steps. Ensure that your new installation is pointing to the correct value of your current STASH_HOME.