Database migration to Oracle fails due to incorrect database encoding
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
The Database migration to Oracle via the Administration -> Systems Settings -> Database console fails.
The following appears in the atlassian-fisheye-DD-MM-YYYY.log
1
ERROR: "The database is not using Unicode. Crucible requires that the database uses a UTF8 encoding to support internalization."Cause
The encoding configuration has been enforced in Fisheye and DB migration will not proceed unless this hard-coded check for UTF-8 has been met.
There is an improvement request open here: FE-3619 - allow users to ignore database encoding warnings to allow users to use an encoding of their choice by suppressing these warnings.
Watch it to be notified of its progress and feel free to comment there.
Resolution
Shutdown Fisheye and edit the <FISHEYE_INST>/config.xml file
Add the database configuration manually as follows:
1
2
3
4
5
6
7
<database type="oracle">
<connection
dialect="<Oracle Database dialect>" driver="<Oracle Driver Class>"
jdbcurl="<Oracle JDBC connection URL>"
password="yourdbpassword" username="yourdbuser" maxPoolSize="20"
minPoolSize="5" driverSource="bundled"/>
</database>Restart Fisheye for the changes to take effect.
Was this helpful?