Heads up! On March 5, starting at 4:30 PM Central Time, our community will be undergoing scheduled maintenance for a few hours. During this time, you will find the site temporarily inaccessible. Thanks for your patience. Read more.
×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.
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. )
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.
Thanks,
Dev G.
>can I proceed with my JIRA upgradation by ignoring these erros
NO.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
Thank you in advance,
Dev G
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Nic Brough -Adaptavist- , could you please reply me asap. Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The answer has not changed - you need to set up your database correctly. Fix the collation settings, and you'll be fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sure @Nic Brough -Adaptavist- , I will fix it and proceed. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have rechecked again , JIRA Database is set up already correct collation, please check below. Please provide me the guidelines, how to fix this.
Thank you,
Dev G
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you so much @Nic Brough -Adaptavist-
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.