Health Check: Database Collation in Oracle
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
ヘルス チェックについて
More about this Health Check
結果の確認
アイコン | 結果 | 意味 |
---|---|---|
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.
ソリューション
これを修正するには、データベース照合を修正する必要があります。最適かつ推奨される方法は、次のとおりです。
- 「Jira をデータベースに接続する」内の手順に従い、必要な照合で新しいデータベースを作成します。
- 「データベースの切り替え」に従い、古い (誤った照合を持つ) データベースから新しい適切な照合を持つデータベースに移行します。
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
データベース | Collation(s) | How to Verify Table Collations | How to Verify Database Collations |
---|---|---|---|
Oracle |
| The table collation check is not done for Oracle as it sets collation on database and session levels only. |
|