Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA Health check shows DataBase errors but they are not actually errors.


Hi Team,

I am trying to upgrade our JIRA form 8.20.1 to JIRA8.2012 version in order to remediate some vulnerabilities. As a pre-check on JIRA, heal check show 2 data base erros. 

DXC JIRA Health check Errors-2022-November.PNG


But, when I checked these in our MS-SQL, they are fine as they expected already. As a pre-upgradation check, this is not allowed for upgradation right( as per the upgration notes. )


DXC JIRA DataBAse Collation Error- Read-committed-snapshot-OFF.PNGDXC JIRA DataBAse Collation Error.PNG


As per the "Run health check" , it is mentioned that...

Jira has several health checks that let you verify whether your Jira instance is ready for an upgrade.


Now my doubt is , can I proceed with my JIRA upgradation by ignoring these erros, or else le tme know the alternative way to proceed this process.



Dev G.


1 answer

0 votes

>can I proceed with my JIRA upgradation by ignoring these erros


With older versions of Jira you could get away with it, but from the mid-7's onwards, it became less tolerant because dealing with mis-configuration just became a massive coding time-waster.

You need to set up the target database in a supportable configuration.  If you do not, your upgraded Jira will, at best, not be able to do reporting or searches properly and possibly fall over without warning, and at worst, you'll just have a completely corrupted database that's so bad Jira won't even start.

Thank you @Nic Brough -Adaptavist-  for the quick reply . As I have mentioned in above already, when I have checked in y Databased everything is set up as required as mentioned in the "Healthe check". There is nothing to fix it,  It menas that, though everything is set up finely, health check gives errors, so could you let me know how to proceed and get rid off this Health check errros. 

Please see below screen shots of my actaul DATA BASE using for our JIRA.


DXC JIRA DataBAse Collation Error- Read-committed-snapshot-OFF.PNGDXC JIRA DataBAse Collation Error.PNG

Hi @Nic Brough -Adaptavist- ,


Now I have fixed isolation level error, but still the collation for JIRA shows error where it is actaully set  the supported from the beginning as  'SQL_Latin1_General_CP437_CI_AI". Unfortunaltey, JIRA health check still shows, Database error on this collation aspect. 

One more point is, in 2 places JIRA check shows "Database' inforamtion. 

One place at "Problems detected" shows error and other place at "Passed check" case shows "Database' as passed check. 

Could you please confirm me how to proceed in this scenario? replying early would be very helpful us. 



DXC JIRA DataBase check.PNGDXC JIRA Collation.PNG


Thank you in advance,

Dev  G

@Nic Brough -Adaptavist- , could you please reply me asap. Thank you

The answer has not changed - you need to set up your database correctly.  Fix the collation settings, and you'll be fine.

Sure @Nic Brough -Adaptavist- , I will fix it and proceed. Thank you.

Hi @Nic Brough -Adaptavist- ,


I have rechecked again , JIRA Database is set up already correct collation, please check below. Please provide me the guidelines, how to fix this. 

JIRA Collation DataBase.PNG


Thank you,

Dev G

You need to look again at your database config.  The collation is still wrong (but that will only break some searches, it is not a huge whoopsie for Jira now

Suggest an answer

Log in or Sign up to answer