Doing a test upgrade of a JIRA from 6.3.8 to 6.4.5 and noticed a warning in the log file that stated:
You are using an unsupported oracle10g collation: WE8MSWIN1252. This may cause some functionality to not work.
The underlying DB is Oracle 11g.
Do I need to change the collation order?
Even if you don't face any problems right away, we strongly recommend against using JIRA with an unsupported collation.
I'd recommend you to follow the steps at https://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+Oracle to setup the database with the right collation.
In case you need Oracle docs to migrate the character set, you might be interested in this one to show to your DBA. He should be aware of this documentation though, but I just wanted to confirm this.
And lastly but not least, changing the character set might implicate into a massive data manipulation. I heavily recommend to a full database backup before this step. DP export should suffice. I'm not sure if you can use the RMAN in such this case but might be worthy to try since RMAN is better than DP export in my opinion.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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!
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