Confluence will not start up because the build number in the Home Directory doesn't match the build number in the Database, after upgrade


アトラシアン コミュニティをご利用ください。


プラットフォームについて: Server と Data Center のみ - この記事は、サーバーおよびデータセンター プラットフォームのアトラシアン製品にのみ適用されます。


When attempting to upgrade to version 5.1.2 and higher of Confluence, the upgrade fails and the following error appearing in the logs:

2013-06-04 07:53:32,448 ERROR [main] [atlassian.confluence.setup.BootstrapApplicationStartupListener] checkConfigurationOnStartup Confluence will not start up because the build number in the Home Directory [<build number>] doesn't match the build number in the Database [<build number>].

The versions represented by the build numbers can be found on this page: Confluence Build Information.


This can be caused by one of the following situations:

  1. If you have just performed a site restore and you are running 5.1.4 or before, you may be encountering this bug: CONF-29758 - Getting issue details... STATUS If your situation matches what is discussed in the description, please follow the workaround provided in that bug report.
  2. At some point in the past an upgrade failed.
  3. The Database has been restored to an earlier version, but the Home Directory hasn't, or vice versa.

In all cases, it means that not all upgrade tasks have run on both the Database and the Home Directory. The information about the version of Confluence is stored in the Database in the confversion table and in the Home Directory in <confluence_home_directory>/confluence.cfg.xml.

The confversion table, which stores information about the versions of Confluence your instance has been upgraded to, is actually a record of the upgrade tasks that have completed successfully. When an upgrade task completes, Confluence puts an entry in the confversion table with the build number of that upgrade task. This is why the build numbers in the confversion table sometimes don't match the actual build numbers of releases; each upgrade task has a build number, and then each release has a build number that is higher than all the upgrade tasks that are required to upgrade to that version.


You can find the build numbers for:
  1. The Database by running:

    select * from CONFVERSION;
  2. The Home Directory by looking in the <confluence_home_directory>/confluence.cfg.xml file:


ソリューション 1

Ideally, both the Database and Home Directory should be restored to a point before the failed upgrade attempt if possible. Once this has been done, ensure that the build number shown in the Database and the Home Directory are the same.

ソリューション 2

If restoring to a point is not possible, manually set the build numbers back to the lower value of the two. For example, If the Home Directory shows 4215, and the Database shows 3289, the Home Directory should be set to 3289, and then perform the upgrade again. This will trigger all upgrade tasks that are in between the Confluence version that the database is using and the version of the installation files that are being upgraded to, as well as upgrade the Database and the Home Directory. To change the value in the Database, delete any entries that have a build number higher than the version in your home directory:

Under no circumstances should one remove all rows/version information from the conf version table


To alter the Home Directory's build number, simply edit the <confluence_home_directory>/confluence.cfg.xml file.

ソリューション 3

If you note that the confluence.cfg.xml file contains the upgraded database build number, but the confversion table shows the row similar to the example below:

456012345664412017-07-04 06:01:42.54Locked for version upgrade to 7201

This suggests the schema upgrades have not completed. This issue can be corrected manually by reverting back the build numbers and using the atlassian.forceSchemaUpdate system property. 

Begin by updating the confluence.cfg.xml build number to match the database build number (ie 6441 in the above scenario).

Next, the versiontag for the most recent build number should be set to null if it is not:

As this involved modification to the database, you are strongly advised to create a backup of your database prior to modification


PLEASE REMEMBER TO COMMIT THE CHANGES (Oracle requires the changes to be committed before they are accepted)

Finally, to force a schema upgrade apply the following system property to the instance (see Configuring System Properties for OS-specific steps): -Datlassian.forceSchemaUpdate=true

Once these changes have been made stop all nodes before allowing a single node to start fully. Then confirm the build numbers now match across the database and the confluence.cfg.xml.  -Datlassian.forceSchemaUpdate=true can then be removed.

最終更新日 2021 年 9 月 10 日


Powered by Confluence and Scroll Viewport.