Health Check: Database Collation in Oracle
Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.
About the Health Check
More about this Health Check
Understanding the Results
What this means
|The session collation of: '<collation>' is supported by JIRA.||The database session collation determined by the health check is supported.|
|The session collation of: '<collation>' is supported by JIRA.|
The Health Check has retrieved the session collation and compared it to one of our supported collations, and it did not match. The database or session collation should be modified to use the correct collation.
The Oracle Collation check confirms if the instance is being accessed with the wrong collation, If a session collation is not set the database collation will be used. However, ensuring that the session collation is correct, is all that impacts JIRA.
To fix this, the database collation needs to be corrected. The best and recommended way to achieve this is:
- Create a new database with the required collation as per the appropriate documentation in Connecting JIRA to a Database.
- Follow our Switching Databases to migrate JIRA from the old databases (with the incorrect collation) to the new one, with the correct collation.
For Oracle Database session issues, the database and session collation configuration can be modified without migrating data. Check with the DBA or product documentation for assistance with this. The Oracle JDBC driver is also capable of automatically setting
NLS_SORT based on the locale of the system. Refer to Database collation health check fails in Jira server with Oracle database for more information about this.
Supported Collations in Oracle Database
|Database||Collation(s)||How to Verify Table Collations||How to Verify Database Collations|
The table collation check is not done for Oracle as it sets collation on database and session levels only.