Migration from 6.2.x direct to Jira 7.x


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". smile





3 answers

1 accepted

1 vote
Answer accepted

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.


Hi Nic,



I must correct myself i go from 6.4.9 directly to 7.3.1.

The first Startup is OK, but when i restart the System again it look like there a Database issues.

U know if it is necessary to add the Attachments to the Version Update?




1 vote

You'll need to read more of the log to see where it's going wrong, but at a glance, you're using an unsupported collation on the database.  Older versions of JIRA would run with it, but later ones need the right collation to be set.

That point i will check. 

When it just the collation than it looks like that the migration from 6.4 goes directly to 7.3.1 without issues.





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

2017-02-24 15:26:53








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


any idea?

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

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 ...

393 views 6 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you