Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-27597

Upgrading Confluence from 3.3.x and below to 4.x directly can fail with "Cannot drop the index 'ATTACHMENTDATA.attch_idver_idx'"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 4.3.7
    • 4.0
    • None

      Problem

      One of the upgrade tasks when going to a 4.x version is to drop the index attch_idver_idx on the ATTACHMENTDATA table. However this index was only added in 3.4.x.

      The upgrade can fail with the following errors in the logs:

      2012-03-22 10:46:33,471 INFO [main] [confluence.upgrade.ddl.HibernateDdlExecutor] executeDdlStatements Executing DDL: drop index attch_idver_idx on ATTACHMENTDATA
2012-03-22 10:46:33,596 ERROR [main] [atlassian.confluence.upgrade.UpgradeLauncherServletContextListener] contextInitialized Upgrade failed, application will not start: Upgrade task com.atlassian.confluence.upgrade.upgradetask.AddUniqueAttachmentIdConstraintToAttachmentDataUpgradeTask@a6cdf5 failed during the SCHEMA_UPGRADE phase due to: StatementCallback; bad SQL grammar [drop index attch_idver_idx on ATTACHMENTDATA]; nested exception is java.sql.SQLException: Cannot drop the index 'ATTACHMENTDATA.attch_idver_idx', because it does not exist or you do not have permission.

      Other notes

      This issue is not always reproducible. So far all of the support requests running into this problem are using SQL Server, so the problem may be limited to that DBMS.

      Workaround

      • Upgrade to 3.4.x or 3.5.x prior to going to 4.x

              slancashire Steve Lancashire (Inactive)
              rchang Robert Chang
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: