Jira - New installation, "old" Database

Hey folks,

i am supposed to migrate my companies Jira installation from one server to another, keeping the old Database, which is running on yet another server.

what i did so far is:

i have set up a new installation of Jira (same version as before, 6.1.5) and after installation, i used the setup wizard to import the .xml backup of the productive db.

Now i should switch the DB to our production one. I figured out the following procedure to do so and it would be nice if someone could tell me, if it will work in that way and if not, what am i supposed to do to make it work:

  1. shut down jira (old and new)
  2. get a backup of the home directory
  3. copy the backup into the "new" jira home folder
  4. make the new connection by using the jira configuration tool / delete or rename the "dbconfig.xml" and use the setup wizard again

greetings from germany

fabian

9 answers

1 accepted

This widget could not be displayed.

Sounds like you got it right, Fabian.Make sure you get a backup of the .XML and the database .bak just in case.

ok my problem is now, that i can access at least jira using browser, but i get this message, which is pretty frustrating aswell

We have detected that JIRA is configured to connect to a database from a previous version of JIRA. If you have just upgraded JIRA, you may need to consult the 3.7 Upgrade Guide.

the end of the logfile is attached to this post

i am desperate, i am at work for 18 hours now and my brain is fried... i hope someone of you guys has a solution for our problem. i will check in 8 hours again, when i will be here at work again

have a good night guys

This widget could not be displayed.

hi mehmet, hi guys

i just told jira, by using the configtool, what is the database (tested successfully) and what is the home-path.

now jira is redirecting to http://jiralockederroror something similar... i am close to desperation. :(

someone familiar with this issue?

This widget could not be displayed.

Bruna got the answer for deadlock.

This widget could not be displayed.


********************************************************************************************************************************************************************************************************
We have detected that JIRA is configured to connect to a database from a previous version of JIRA. If you have just upgraded JIRA, you may need to consult <a href="http://confluence.atlassian.com/display/JIRA/JIRA+3.7+Upgrade+Guide">the 3.7 Upgrade Guide</a>.
********************************************************************************************************************************************************************************************************

2014-08-11 22:47:28,125 localhost-startStop-1 FATAL [atlassian.jira.startup.DatabaseChecklistLauncher] Build178SchemaCheck failed: We have detected that JIRA is configured to connect to a database from a previous version of JIRA. If you have just upgraded JIRA, you may need to consult <a href="http://confluence.atlassian.com/display/JIRA/JIRA+3.7+Upgrade+Guide">the 3.7 Upgrade Guide</a>.
2014-08-11 22:47:28,125 localhost-startStop-1 FATAL [atlassian.jira.startup.DatabaseChecklistLauncher] Database startup check failed.
2014-08-11 22:47:28,144 localhost-startStop-1 INFO [jira.config.database.DatabaseConfigurationManagerImpl] Now running Post database-configuration launchers
2014-08-11 22:47:28,459 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Name is PostgreSQL
2014-08-11 22:47:28,460 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Product Version is 8.3.13
2014-08-11 22:47:28,460 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Driver Name is PostgreSQL Native Driver
2014-08-11 22:47:28,460 localhost-startStop-1 INFO [core.entity.jdbc.DatabaseUtil] Database Driver Version is PostgreSQL 9.0 JDBC4 (build 801)

This widget could not be displayed.

The database scheme changes between two versions cause these type or errors. What I would do is to:

1. Use an empty database and set JIRA up with that.

2. Import XML you backed up from earlier version

See if that works. Sometimes little things frustrate too much, been there done that. Hang in there.

good morning guys,

now i was finally able to make jira work now, it was an issue in the dbconfig.xml.

I can login, the profile pictures and probably also attachments are available, but i cannot see a single issue...

greetings

This widget could not be displayed.

so re-indexing solved the problem of the missing issues :)

now i have just to switch to ssl and i am done ... i cannot believe it

thanks alot guys!!!

This widget could not be displayed.

so everything is working now!

do i have to close this issue?

greetings

This widget could not be displayed.

Glad about it, Fab!

Since this is a Forum, there's no need to close the case. I just suggest you to click on the "Accept" button to have the the answer accepter. Right below the vote/downvote options for the answers. :)

Cheers,

Giu

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

97 views 1 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