jira build version and db build version inconsistency

[ravi]

we have upgraded jira test server from 6.4.5  to 7.9.2 which should not be done as per application team.

So tried to revert back the application to 6.4.5 but jira fails to start with below message

Failed to start JIRA due to a build number inconsistency. The data present in your database is newer than the version of JIRA you are trying to startup. Database version is: 79002 JIRA app version is: 64020 Please use the correct version of JIRA. You are running: 6.4.5#64020-sha1:78acd6c502bd8e526a3f0032b770e55d6f3a3b0f

2018-08-21 16:00:5

[Nic Brough -Adaptavist-]

Sounds like you "downgraded" the application but did not restore the pre-upgrade database before you started it.

Stop Jira 6.4, reload the pre-upgrade database and then restart it, you should find it woks fine.

[ravi]

unfortunately I dont have the old database to reload

[Nic Brough -Adaptavist-]

Ah.  Ok.  You only have one realistic option now - roll-forwards.

Install an empty Jira 7.9.2 with a separate database, get the basics working, then stop it, repoint it at the 7.9.2 database you have with data in it, restart it and re-index it all.

Without a backup of the pre-upgrade database, there's no way back (without potentially months or years of work to downgrade the data, or just starting with an empty 6.4.5)

[ravi]

Nic ,

Thanks for your reply.

In that case as suggested above it would work with only 7.9.2 (its already working with 7.9.2) but application team requirement is to run older version 6.4.5 for testing their application.

I have also tried -Djira.downgrade.allowed flag but it did not work.

Is there any other alternatives to get it work with 6.4.5 (I know its tough)

1) Is there any possibility to downgrade Database version is: 79002 to match jira version 64020 in the database.Will it work if we match that version number in database.

2) If I create a new db and point my jira 6.4.5 to that new db  and upload the 7 database into it and restart jira. will it work?

[Nic Brough -Adaptavist-]

Again, without a backup of the pre-upgrade database, there's no way back.  Not without potentially months or years of work to downgrade the data, or just starting with an empty 6.4.5.

[ravi]

Any help on this will be appreciated