SonarQube 6.7.1 enforcing UTF-8 database charset on existing database.

[Shiva hari kumar Balasubramanian]

Hi Devs,

As per the jira ticket https://jira.sonarsource.com/browse/SONAR-6171  SonarQube should not enforce existing installation to move to UTF-8. But I'm struggling to upgrade from 5.6.7.

I'm able to upgrade to SQ 6.7, facing this problem only in SQ 6.7.1

I raised this in SO, https://stackoverflow.com/q/48659889/2068802 but not the kind of response I wanted. I hope I the right answers here.

ERROR web[][o.s.s.p.Platform] Web server startup failed: Oracle NLS_CHARACTERSET does not support UTF8: WE8ISO8859P1




Thanks,

Shiva B

[G. Ann Campbell]

Hi Shiva,

Can you confirm that with the 6.7 upgrade you performed the database migration & successfully "ran" SonarQube (run analyses, use UI, ...)?

Thx,

Ann

[G. Ann Campbell]

Hi again,

Can you also confirm that your 6.7.1 instance is an upgrade from the instance you previously upgraded from 4.5.4 to 5.7 to 6.7?

Thx,

Ann

[Shiva hari kumar Balasubramanian]

Hi Ann,

Yes, I'm able to upgrade to 6.7 without problem.

My upgrade chain looks something like this,

4.5.4 => 5.7 => 6.7 => 6.7.1

In this 6.7 => 6.7.1 broke.

[Simon Brandhof]

The error that you face is not specific to 6.7.1. It's about the DB character set that is not UTF-8 compatible. You should double-check that your 6.7.1 instance is configured with the correct DB schema.

[Shiva hari kumar Balasubramanian]

But as per this ticket SonarQube should not force existing installation to migrate to UTF 8

https://jira.sonarsource.com/browse/SONAR-6171

[Shiva hari kumar Balasubramanian]

Hi,

Any Update or traction? Be open if this is going to be the end for rest of encoding standards. We are using Western European as if applies to our locale, it is going to be costly migration for us to migrate to UTF-8

[Simon Brandhof]

The UTF8 check is supposed to be executed only on fresh installations, so I'm surprized that you have the failure. Could you send the full logs please? 

Note that at a point of time you should plan to move to a UTF8 database. That should avoid unexpected behaviors.

[Shiva hari kumar Balasubramanian]

I'm not able to replicate the issue now. Please close this, if I face it again will raise a new thread. Thanks

Shiva 

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/jYRzfL5IaBk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/00a72a28-b3d1-487e-83e4-9bacad4cb406%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[G. Ann Campbell]

Thanks for the follow up. I'm glad this is working for you now.

Ann

On Thursday, 29 March 2018 10:36:23 UTC-4, Shiva hari kumar Balasubramanian wrote:

I'm not able to replicate the issue now. Please close this, if I face it again will raise a new thread. Thanks

Shiva 

On Wed 21 Mar, 2018, 18:18 Simon Brandhof, <simon.brandhof@sonarsource.com> wrote:

The UTF8 check is supposed to be executed only on fresh installations, so I'm surprized that you have the failure. Could you send the full logs please? 

Note that at a point of time you should plan to move to a UTF8 database. That should avoid unexpected behaviors.

On Tuesday, 20 March 2018 19:04:23 UTC+1, Shiva hari kumar Balasubramanian wrote:

Hi,

Any Update or traction? Be open if this is going to be the end for rest of encoding standards. We are using Western European as if applies to our locale, it is going to be costly migration for us to migrate to UTF-8

On Tuesday, 6 March 2018 10:27:30 UTC+5:30, Shiva hari kumar Balasubramanian wrote:

But as per this ticket SonarQube should not force existing installation to migrate to UTF 8

https://jira.sonarsource.com/browse/SONAR-6171

--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/jYRzfL5IaBk/unsubscribe.

To unsubscribe from this group and all its topics, send an email to sonarqube+unsubscribe@googlegroups.com.