-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 3.5.9
-
Component/s: Server - Upgrade Manager
During upgrade, some upgrade tasks that add new constraints attempt to drop constraints that might not exist for the current DB. When this happens, the log will contain messages similar to:
2011-10-19 10:56:23,196 ERROR [main] [confluence.upgrade.ddl.HibernateAlterTableExecutor] alterTable Failed to run alter table commands 2011-10-19 10:56:23,196 INFO [main] [confluence.upgrade.upgradetask.BandanaKeyUniqueConstraintUpgradeTask] doUpgrade Ignoring non-existence of bandana_unique_key constraint
The first error message should be downgraded to debug, if it is kept at all.