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

'KEYSTORE' table doesn't exist. BackupEntities couldn't backup database data

    XMLWordPrintable

Details

    Description

      Upon Confluence upgrade to 2.7 or later, admin may discover that the KEYSTORE table does not exist.

      An upgrade misconfiguration is known to can cause this. For example:

      1. Admin created a test Confluence instance of the latest version and new database, then shut it down
      2. Admin imported production database into this new instance
      3. Admin copied production instance's Confluence Home but kept the test instance's confluence.cfg.xml. This xml file contains the target version's build number.
      4. Admin started test instance in the hope that this will upgrade Confluence.
      5. Because Confluence see that the build number in confluence.cfg.xml is the same as the running Confluence version, the upgrade is skipped.

      Step 3 is wrong. The confluence.cfg.xml should also be reverted to the old build number (click here for Confluence Build Information).

      Sample error
      ERROR [DefaultQuartzScheduler_Worker-6] [confluence.importexport.impl.BackupExporter] backupEntities Couldn't backup database data.
org.springframework.jdbc.BadSqlGrammarException: Hibernate operation: Could not execute query; bad SQL grammar []; nested exception is com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table 'confluencedb271.KEYSTORE' doesn't exist
Caused by: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table 'confluencedb271.KEYSTORE' doesn't exist
	at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1027)

      This issue can be prevented had we have CONF-18085 implemented.

      See also CONF-13798

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. CONFSERVER-18084 ImageDetails table not created during upgrade to 3.1

          • Medium - Medium priority issues
          • Closed
          is superseded by

          Suggestion - CONFSERVER-18085 Need an integrity checker to check all required database tables exist after an upgrade

          • Gathering Interest
          relates to

          Bug - A problem which impairs or prevents the functions of the product. CONFSERVER-8876 DB schema updater should abort if there is a problem executing SQLs

          • High - High priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhartono Roy Hartono [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: