migrating from ondemand to onpremesis - database version issue

Cullen Philipps1

Version 6.3.3.1 onPremesis server installed on CentOS 6.5 linux

After importing our backup from our ondemand site, the jira service will not start. The following is in the Jira (tomcat log):

****************************************************************************************************

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: 64000

JIRA app version is: 6331

Please use the correct version of JIRA. You are running: 6.3.3#6331-sha1:d919e5c6aac4bdb845e5512db42aa18387f6a299

****************************************************************************************************

How to I overcome this version issue and will it compromise my data?

Alexey_Rjeutski__Polontech_

Hi, we have got that problem serveral times. The problem is that the version on onDemand often larger that latest release version on standalone. We do the following - manually edit the xml backup and change the version and build number so the xml restore will "eat" backup from improper version. There are often the problems with changes - so we do the drop of columns that are not part of database anymore and create empty columns using linux regexp change. But there is high probability that you will have to change only those numbers. Please note, that it is often that you are unable to migrate due to plugin version match - either do the same either disable / remove plugin at target standalone instance. I recommend either wait until new release is comming so you will get the match between ondemand and standalone, either do the test migration by the method I've sent to you and then deside if you are ok with the imported data.