Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-66190

Database truncation error when inserting certain translated messages

XMLWordPrintable

      Summary

      When a health check fails, the translated Description and Failure Reason strings are inserted into the table AO_2F1435_HEALTH_CHECK_STATUS. In some languages, the translated string can exceed the default column size.

      This has been confirmed for the following languages:

      1. French
      2. Russian

      Steps to Reproduce

      Trigger health check error with the following message

      Vérifie le nombre maximum de processus (threads) que le compte d'utilisateur peut exploiter simultanément. Le nombre maximum de processus est défini par le système d'exploitation et s'il est trop faible vous risquez de vous heurter à des problèmes de performance et à des erreurs dues au manque de mémoire (OOM).

      Alternatively, directly insert the following into DB

      insert into dbo.AO_2F1435_HEALTH_CHECK_STATUS (STATUS_NAME,DESCRIPTION) VALUES ('test3','Vérifie le nombre maximum de processus (threads) que le compte d''utilisateur peut exploiter simultanément. Le nombre maximum de processus est défini par le système d''exploitation et s''il est trop faible vous risquez de vous heurter à des problèmes de performance et à des erreurs dues au manque de mémoire (OOM).');

       

      Expected Behavior

      JIRA is able to insert the health check error into DB.
       

      Actual Behavior

      The insert will fail - and the error message will vary by database type.

      Workaround

      There is no valid workaround at this time. While it would be possible to alter the database column type (so it can accomodate a larger string) this is not the recommended approach. In Active Objects Tables, the database schema is more abstracted than traditional application tables - making adjustments directly to the schema inadvisable. If you do make changes, ensure you've got a full database backup; and that changes are tested before applying to production.

            [JRASERVER-66190] Database truncation error when inserting certain translated messages

            Tom Davies added a comment -

            This is tracked as https://ecosystem.atlassian.net/browse/ATST-919

            Tom Davies added a comment - This is tracked as https://ecosystem.atlassian.net/browse/ATST-919

            Dominique Jean-Prost added a comment -

            I had to reapply the manual database change after upgrading to the last Jira version this morning. Will this issue be soon be fixed ?

            Dominique Jean-Prost added a comment - I had to reapply the manual database change after upgrading to the last Jira version this morning. Will this issue be soon be fixed ?

            Bulanov Maxim added a comment -

            same problem with Oracle

            workaround for this problem

            ALTER TABLE SERVICEDESK.AO_2F1435_HEALTH_CHECK_STATUS MODIFY FAILURE_REASON VARCHAR2(469)

            Bulanov Maxim added a comment - same problem with Oracle workaround for this problem ALTER TABLE SERVICEDESK.AO_2F1435_HEALTH_CHECK_STATUS MODIFY FAILURE_REASON VARCHAR2(469)

              Unassigned Unassigned
              llee2@atlassian.com Lenard Lee
              Affected customers:
              2 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: