Summary

If the Oracle database is configured for NLS_SORT="GERMAN", but all JIRA sessions are changed to "BINARY" by a logon trigger, the database collation read still incorrectly reads the collation.

Environment

• Oracle
• NLS_SORT of German
• JIRA sessions changed to BINARY by a login trigger.

  Steps to Reproduce

1. Set up expected environment.
2. Start JIRA.

   Expected Results

The collation is correctly read.

Actual Results

The collation is read as incorrect and errors are thrown in the logs as per below:

2016-05-20 07:18:01,269 JIRA-Bootstrap WARN      [c.a.j.appconsistency.db.CollationCheck] 
    
    ****************************************************************************************************
    You are using an unsupported oracle10g collation: GERMAN. This may cause some functionality to not work.
    Please use BINARY as the collation instead.
    ****************************************************************************************************

Notes

1. This is a spurious error and can be ignored. If unsure, use the Database Collation Health Check to verify the collation is correct (it will take into account the session collation as the collation is checked with different SQL).

1. Starting with JIRA 7.4, a new functionality is introduced which is the Johnson page where a startup check is performed and JIRA is locked upon startup to return an error or warning. Due to the nature of this error, JIRA will be locked and the following warning will be shown during startup:
   
   It is safe to proceed with clicking on "Ignore all warnings and continue" in this scenario.