You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
ofcourse possible that I did something wrong but:
This page https://confluence.atlassian.com/adminjiraserver073/connecting-jira-applications-to-mysql-861253043.html explains step by step how to configure and connect MySQL for JIRA.
But it wasn't complete and I probably can prevent others from having the same trouble:
For getting JIRA to correctly startup instead of giving me a white error page I had to additionally do the following steps:
CREATE USER '<username>'@'<host>' IDENTIFIED BY "<pasword>";
CREATE DATABASE public CHARACTER SET utf8 COLLATE utf8_bin;
- 3. here you can skip the "IDENTIFIED BY" now since we already added the user in 1. But you have to grant the permissions for both databases! (I just granted ALL to make it simple)
GRANT ALL PRIVILEGES ON <jiradb>.* TO '<username>'@'<host>';
GRANT ALL PRIVILEGES ON public.* TO '<username>'@'<host>';
Go on with the rest of the manual. But then after finishing in the <jiraDataFolder( e.g. /var/...)>/dbconfig.xml you will still notice the line
and actually the catalina log complains that this name is only allowed for the H2 database type in non-productive mode (so it would not help to add the database with the name PUBLIC in capitals).
So all you have todo for finally get it running is to change it to
or whatever you called the second database and restart JIRA e.g.
sudo service jira restart
This finally worked for me and I could re-import our old (backup) database data into the new mysql setup.