today i have try in a test environment to upgrade a JIRA 6.2.4. Version directly to JIRA 7.3.x
I get the effect that JIRA starts clear and all Data is available.
But when i restart JIRA after this migration, JIRA won't start again, it looks like the data is not consistent.
The Upgrade self i try it with out the Migration of the Attachments because to sync more then 200GBs will take to much time.
So, it is better to migrate from 6.4. to 7.0. to 7.3.1 to solve this, or ist this a Problem that i don't have used the attachments and the Upgrade task was not finished clearly?
Maybe someone has make the same "mistake".
That's too large a jump over the 6-7 hurdle. Officially, you should really go to 6.4, then 7.0, but you will probably find you can go a bit further.
The largest jump I've seen work in one go is from 6.3 to 7.1 (I tried 7.2, but there were too many problems).
6.4 to anything up to 7.2 seems to work absolutely fine, in my experience, and I got part way into a 6.4 to 7.3 upgrade that was looking healthy before we changed track slightly.
Your mileage may vary - I'd plan the worst case, 6.3 -> 6.4 -> 7.0 -> 7.3, but actually test 6.3 -> 6.4 -> 7.3 and run with it if it's healthy.
I have Upgraded from 6.4.9 to 7.0 to 7.3.1.
After the Migration JIRA comes cleary up.
The Data looks fine.
But when i restart the System i get follow error:
There is a problem with your JIRA access.
Unexpected exception during JIRA startup. This JIRA instance will not be able to recover. Please check the logs for details
I get also this error message:
You are using an unsupported postgres72 collation: en_US.UTF-8. This may cause some functionality to not work.
Please use POSIX.UTF-8 or C.UTF-8 or C or POSIX as the collation instead.
2017-02-24 16:38:48,762 JIRA-Bootstrap ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: org/bouncycastle/util/encoders/DecoderException
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs