You are on page 1of 4

It seems like there is a bug which is already reported:

https://jira.atlassian.com/browse/JRA-41886
I have fixed it by clicking on FIX. Now the integrity check shows all passed.

FOR SECOND TEST:

As provided in the URL:


https://confluence.atlassian.com/jirakb/health-check-database-collation790955315.html#HealthCheck:DatabaseCollation-Resolution
I have ran the commands and below is the output for the commands:
[postgres@XST0306 ~]$ psql jiradevdb postgres
psql (9.3.14)
Type "help" for help.
jiradevdb=# SELECT DISTINCT COALESCE(collation_name, 'DEFAULT')
collation_name FROM information_schema.columns WHERE table_schema =
Current_schema();
collation_name
---------------(0 rows)
jiradevdb=# SELECT datcollate FROM pg_database WHERE datname =
Current_database();
datcollate
-----------C
(1 row)
jiradevdb=#

The SQL Statement for table doesnt seem to return any collation_name which I
believe might be the issue.

And from the support tools we see the below errors:

For creation of Database we used the below SQL command:


CREATE DATABASE jiradevdb WITH ENCODING 'UNICODE' LC_COLLATE 'C' LC_CTYPE
'C' TEMPLATE template0;

You might also like