the build number in the database [7202] doesn't match either the application build number [8100]
Asked by yang lei:

When I try to restore my database,there is an error "Confluence cluster node will not start up because the build number in the database \[7202\] doesn't match either the application build number \[8100\] or the home directory build number \[8100\]",but now I change the home directory build number to 7202,there is another error : org.apache.velocity.exception.MethodInvocationException: Invocation of method 'isShowSignUp' in class com.atlassian.confluence.user.actions.LoginAction threw exception java.lang.NullPointerException: Application cannot be null at /login.vm\[line 6, column 28\].

I don't know how to solve it.


Answers:
author: Nic Brough -Adaptavist-
body: You have restored a database that is for an older version of Confluence than the one you have in the cluster.

This will not work, and you can't just change the ID in a file or table to match, that's just lying to the software about what it expects, and will make it fall over because the data is still going to be the wrong shape.

You need to restore the old data and point a confluence of the right version at it. Then upgrade that Confluence to the desired version.

See <https://developer.atlassian.com/server/confluence/confluence-build-information/> for the list of build/version numbers if you need them

comments: author: yang lei
body: Thank you,this helped me,and I update the application number in datebase,it works.<https://confluence.atlassian.com/confkb/confluence-will-not-start-up-because-the-build-number-in-the-home-directory-doesn-t-match-the-build-number-in-the-database-after-upgrade-376834096.html>


author: Nic Brough -Adaptavist-
body: ARGH! NO!

That is absolutely the one thing I said NOT to do. You now have a corrupted and unsupportable data set that could break at any time.

Please, restore a backup and upgrade it properly.


author: Maria Bonello
body: Is there a way how you can cater for this before the upgrade in order to avoid such issue?

comments: author: Nic Brough -Adaptavist-
body: I do not understand what you are asking.

There is nothing to "cater for" here - you cannot restore databases like this.

If you're doing an upgrade, you take an existing, working Confluence and upgrade it. If you're doing this on another machine, such as a test server, then you start with a copy of the existing working Confluence and upgrade that.

You do not restore an old database and point a newer Confluence at it. Or vice-versa.


author: Maria Bonello
body: I don't know if I should ask in this question but currently I'm doing an upgrade in a test instance and I experienced the same error twice regarding the build number. I don't know what I'm doing wrong. The database also indicates 'lock_for_upgrade_to_8301' in the CONFVERSION table for the last entry. I didn't do any changes to the database but I changed the build number from the confluence.cfg.xml file but I'm still having the same error.

So I'm asking if I can do anything such as configuration changes before performing the upgrade so that I will not have the error again.


author: Nic Brough -Adaptavist-
body: You have taken a copy of a Confluence database and pointed the wrong version of Confluence at it.

Stop your test Confluence. Go look at the exact version of Confluence that your data came from.

Go find a download of the exact same version of Confluence, and install that on your test system. This will fix the error, and put you in a position where you can now start upgrading.

\>I changed the build number from the confluence.cfg.xml file

Again, do not do anything like this. Do not bodge numbers anywhere, you will break it all.


author: Neha Singh
body: Hello Guys,

We have upgraded the confluence from 6.13.10 to 7.4.4, and while accessing the site, we got this error "Confluence cluster node will not start up because the build number in the database \[7701\] doesn't match either the application build number \[8401\] or the home directory build number \[7901\]".

What we can do from here, I guess, we don't have to perform manually changes to DB or home directory


author: Nic Brough -Adaptavist-
body: This error message is telling you that you have NOT upgraded Confluence, you've taken a 6.9 installation, tried (and not succeeded) in uograding it to 6.14, then pointed a 7.4 installation at it.

Somewhere, you've made a right mess of this. The best thing you can do is shut the whole install down, then create a new empty node at version 6.9 and point it to the database, check it is working, and then upgrade it properly, not with randomly sticking versions on disks and not bothering to do the upgrade.


Tags: confluence-server

server