nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Plan Your Upgrade" giving incorrect info on pre-upgrade checks

Michael Thompson

Hi everyone,

I just saw the notice regarding the release of Jira Server 8 and the new "Plan Your Upgrade" tool. I am currently running Jira Server 7.12.3 with an Oracle 12c R2 database, and I ran the tool to check for an upgrade to Jira 8.0.0.

Everything except step 1 looks good. In the pre-upgrade check, it tells me that I'm using an unsupported database. However, when I click the "learn more" link, I see that Jira 8 supports Oracle 12c R1. I have the correct JDBC driver installed as well.

All I can think of is the the check is looking in the "Database Type" field, which must list oracle10g (anything else throws an exception and Jira will not start).

Is this a bug in the planning tool? My system specs relating to database are listed in the attached image.

Accepted answers

Dave Theodore [Coyote Creek Consulting]

Always check the supported platforms page to make sure you are running a supported configuration. As you can see from the Jira 7.12 supported platforms page, you are not running a supported configuration. I expect this is what the tool is complaining about. Only 12c R1 is supported on Jira 7.12 and 8.0. It may work, but it would be best to run a supported platform.

All comments

Dave Theodore [Coyote Creek Consulting]

Michael Thompson

Wow, thanks Dave. I assumed that if R1 was supported that R2 must be as well.

With any luck this won't be an issue. I don't plan on upgrading until around May (after a bug fix or two is released), and management is pushing to move Jira off of Oracle and onto Postgres for the cost savings in licensing.

Dave Theodore [Coyote Creek Consulting]

When you move to Postgres, be sure to watch the logs when importing your data. We've seen cases where table constraints are different and the import fails because of it. You may need to increase some constraints in order to get the data to import. To make troubleshooting easier, start with an empty log and then copy it somewhere so you can isolate the logging from each import attempt.

Michael Thompson

Sounds good, I've started my research now.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

oracle