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; } } }

Move Jira from Oracle 12c to 19c

Sue Bridges

I am looking to move our 9.4 SERVER Jira from Oracle 12c to 19c on Windows. The actual Jira release doesn't matter as the steps will be the same for any, but just want to check.

Presumably, in simple terms this is accomplished as follows:

1) Create new 19c database for Jira to live in and start it up.
2) Export Jira data from within current 12c Jira. Attachments and nothing else changing in the directories for Atlassian.
3) Point existing Jira to new Oracle database via …\Atlassian\JIRA\bin\config.bat

4) Shutdown/startup Jira? – not sure on this bit

When I log into Jira, I would expect it to have no issues once linked to new DB

5) Import Jira data from above so now good to go (it will pick up the Attachments as before),

Have I missed anything?

Accepted answers

Robert Wen_Cprime_

Hello @Sue Bridges !

It appears you're using a hybrid of the methods outlined in the following article:

https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html

If you can't get your Oracle DBA to copy and upgrade the database from Oracle 12C to Oracle 19c, you should probably treat this as the second method in the article (moving to different type of database), where you create a blank 19c database and use a Jira XML backup to populate it.

All comments

Robert Wen_Cprime_

Hello @Sue Bridges !

It appears you're using a hybrid of the methods outlined in the following article:

https://confluence.atlassian.com/adminjiraserver/switching-databases-938846867.html

Sue Bridges

Hi, thanks for the doc link - just what I needed.

I have done a Migrating across servers before, and looking at my notes, it fits with the second section Migrating Jira's data to a different type of database server. Though it's on the same server, it should work for the new database. Upgrading Oracle can be a right hassle. Assuming the Jira import tool is as good as ever, it's easier to create a new DB.

However, I have to query why I would want to delete the dbconfig.xml file in step 5 though?

Can't I just modify the existing via config.bat and test the connection (I've done that before). Then for the Jira restart it will just need the import?

Robert Wen_Cprime_

The reason you delete the dbconfig.xml (when I've done this I've just renamed it dbconfig.xml.bak) is so that when Jira starts up, it assumes that there's no database so it will go into "setup mode" and allow you to set up the new database connection and perform the restore of the XML backup.

Sue Bridges

Thanks for the update and appreciate the speedy response!

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