After upgrading a 5.1.4 to latest 5.2.5, the installation's schema upgrade fails due following upgrade step and therefor all following queries. The complete application only prints out a standard Tomcat error page.
I have set the priority to Major, but actually the application is not usable with 5.2.5 (perhaps since 5.2?) under some circumstances of data?
013-09-30 13:58:59,819 INFO [main] [springframework.web.context.ContextLoader] initWebApplicationContext Root WebApplicationContext: initialization completed in 19535 ms
2013-09-30 13:59:01,786 INFO [main] [confluence.upgrade.upgradetask.LoginInfoDuplicateEntryRemovalUpgradeTask] doUpgrade No duplicate logininfo rows found. No action necessary.
2013-09-30 13:59:02,080 INFO [main] [atlassian.confluence.upgrade.UpgradeTask] doUpgrade Finding rows with mixed case username references in LINKS table
2013-09-30 13:59:02,124 INFO [main] [atlassian.confluence.upgrade.UpgradeTask] doUpgrade Finding rows with mixed case username references in TRACKBACKLINKS table
2013-09-30 13:59:02,126 INFO [main] [atlassian.confluence.upgrade.UpgradeTask] doUpgrade Finding rows with mixed case username references in FOLLOW_CONNECTIONS table
2013-09-30 13:59:02,148 ERROR [main] [atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized Upgrade failed, application will not start: Upgrade task com.atlassian.confluence.upgrade.upgradetask.LowerCaseUsernameReferencesUpgradeTask@409f3aab failed during the SCHEMA_UPGRADE phase due to: Table 'LABEL' has more than one primary key
com.atlassian.confluence.upgrade.UpgradeException: Upgrade task com.atlassian.confluence.upgrade.upgradetask.LowerCaseUsernameReferencesUpgradeTask@409f3aab failed during the SCHEMA_UPGRADE phase due to: Table 'LABEL' has more than one primary key
I would suggest it lools like a similar one like CONF-30380 which was MySQL only.
Bug
Medium
![[Atlassian Support System]](/images/icons/generic_link_16.png "[Atlassian Support System]")
CSP-110582
You do not have permission to view this issue
