Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11169

Fixing NLS_SORT for Jira Agile queries

XMLWordPrintable

      JAG needs a better way of fixing the NSL_SORT in Oracle DB.
      Right now we are doing a forced NSL_SORT over the RANK column dropping the performance.

      Possibilities:

      1. Document this
      2. Do a migration script that force the database to NLS_SORT=Binary
      3. Try to fix the index or the column to use the proper NLS_SORT.

      The difference between this ticket and GHS-11162 is that we should take off the NLS_SORT while the other is about removing the function from the code.

            [JSWSERVER-11169] Fixing NLS_SORT for Jira Agile queries

            Michael Tokar added a comment -

            After discussion with ckhatchikian we decided that this issue is mainly incorporated by the linked JRA issue.

            GHS-11162 covers any fixes that need to be made in the JIRA Agile codebase.

            Therefore we are resolving this issue.

            Michael Tokar added a comment - After discussion with ckhatchikian we decided that this issue is mainly incorporated by the linked JRA issue. GHS-11162 covers any fixes that need to be made in the JIRA Agile codebase. Therefore we are resolving this issue.

            Carlos Khatchikian added a comment -

            I got this in the jdbc connection:

            <!-- sql to call when connection is created -->
<new-connection-sql>select 1</new-connection-sql>

            and someone use it to force the NSL_SORT there like this:

            BEGIN
EXECUTE IMMEDIATE 'ALTER SESSION SET NLS_SORT = 'BINARY_CI';
END;

            I think that is configured in the JDBC and could help a bit

            Carlos Khatchikian added a comment - I got this in the jdbc connection: <!-- sql to call when connection is created --> < new -connection-sql>select 1</ new -connection-sql> and someone use it to force the NSL_SORT there like this: BEGIN EXECUTE IMMEDIATE 'ALTER SESSION SET NLS_SORT = ' BINARY_CI'; END; I think that is configured in the JDBC and could help a bit

            Carlos Khatchikian added a comment -

            Another suggestion would be to have a checker in JAG that puts a header saying that the NLS_SORT is not the correct one and a link to a doc.
            That would be a good solution cause I don't see how to do a proper migration.

            Carlos Khatchikian added a comment - Another suggestion would be to have a checker in JAG that puts a header saying that the NLS_SORT is not the correct one and a link to a doc. That would be a good solution cause I don't see how to do a proper migration.

              Unassigned Unassigned
              ckhatchikian Carlos Khatchikian
              Affected customers:
              0 This affects my team
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: