Upgrade problem with Oracle

Mario Wörndl January 31, 2019

We were upgrading JIRA Software from 7.4 to 7.13.

We used Oracle driver ojdbc8.jar that signed in with

 Database Driver : Oracle JDBC driver - 12.2.0.1.0

Before upgrade procedure starts we got following error:

2019-01-30 15:16:00,320 JIRA-Bootstrap ERROR [c.a.jira.upgrade.UpgradeLauncher] No upgrade is being performed due to detected inconsistencies. Your database is using an unsupported collation

Calling the URL in Browser gave us some information about changing Collation in Postgres.

Oracle Database Collation seemed to be GERMAN

Found following article: https://confluence.atlassian.com/jirakb/health-check-database-collation-in-oracle-943951532.html -- This is probably the check that is done for upgrade, isn't it?

Due to https://confluence.atlassian.com/jirakb/health-check-the-session-collation-is-unsupported-by-jira-in-oracle-database-828788420.html we set java properties:

-Duser.language=en -Duser.country=US 

This had no effects.

Do I have other possibilities than user.language and user.country, e.g. in connection string?

How to decide if we have to change Oracle database?

How can following three statements show what to change on database?

SELECT * FROM nls_database_parameters WHERE parameter IN ('NLS_SORT');
SELECT * FROM nls_session_parameters WHERE parameter IN ('NLS_SORT');
SELECT COALESCE(value, (SELECT value FROM nls_database_parameters WHERE parameter = 'NLS_SORT')) FROM nls_session_parameters WHERE parameter = 'NLS_SORT'

 

2 answers

0 votes
Snorre Selmer October 11, 2019

We have the same issue.

Using the article at https://confluence.atlassian.com/jirakb/database-collation-health-check-fails-in-jira-server-with-oracle-database-828788420.html and running each of the SQL statements in order, I've found that:

nls_database_parameters = BINARY

nls_session_parameters = NORWEGIAN

...and the last statement also returns NORWEGIAN.

I'm wondering if there's a safe way to change the session parameter live or if we have to do a fresh import from the XML backup or similar to get this sorted.

0 votes
Florian S September 6, 2019

We have the same problem :-/

Suggest an answer

Log in or Sign up to answer