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

Lexorank Cleanup Scheduler broken on Oracle databases

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 9.11.0, 9.11.1
    • Lexorank
    • 9.11
    • 2
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 29 Sep 2023

      Dear Customers,

      Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog.

      Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

      Best regards

      Maria Mikołajczak

      Software Engineer Jira DC

      Show
      Atlassian Update – 29 Sep 2023 Dear Customers, Thank you for taking the time to file and comment on this issue. Feedback like yours helps us release valuable Jira features that solve problems for a greater customer base. To that end, we aim to keep our issues up-to-date so they accurately reflect current customer needs. Based on the impact, we’ve decided to move this issue to our short-term backlog. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Maria Mikołajczak Software Engineer Jira DC

      Issue Summary

      In Jira 9.11.0, the Lexorank cleanup scheduled job was added in order to fix the  JSWSERVER-13098 bug, however, this job is broken on Oracle databases.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Install or upgrade to Jira 9.11.0 with Oracle database.
      2. Access the Scheduler details page

      Expected Results

      The Lexorank Cleanup Scheduler (com.atlassian.greenhopper.manager.lexorank.LexoRankCleanupScheduler) is working with no errors.

      Actual Results

      The Lexorank Cleanup Scheduler (com.atlassian.greenhopper.manager.lexorank.LexoRankCleanupScheduler) is failing with the following error message:

      RuntimeException: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist SQLSyntaxErrorException: ORA-00942: table or view does not exist OracleDatabaseException: ORA-00942: table or view does not exist
      Scheduler administration 

      The below exception is thrown in the atlassian-jira.log file:

      2023-09-26 12:46:17,509+0000 Caesium-1-3 ERROR      [c.a.scheduler.core.JobLauncher] Scheduled job with ID 'com.atlassian.greenhopper.manager.lexorank.LexoRankCleanupScheduler' failed
java.lang.RuntimeException: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
    ... 14 more
Caused by: Error : 942, Position : 78, Sql = SELECT lexorank."FIELD_ID" FROM "AO_60DB71_LEXORANK" lexorank LEFT OUTER JOIN "customfield" cf ON lexorank."FIELD_ID" = cf.id WHERE cf.id IS NULL, OriginalSql = SELECT lexorank."FIELD_ID" FROM "AO_60DB71_LEXORANK" lexorank LEFT OUTER JOIN "customfield" cf ON lexorank."FIELD_ID" = cf.id WHERE cf.id IS NULL, Error Msg = ORA-00942: table or view does not exist

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

        1. image-2023-09-26-09-59-20-844.png
          image-2023-09-26-09-59-20-844.png
          75 kB

              Unassigned Unassigned
              7d74d3b1a350 Rodrigo Jose Zaparoli
              Votes:
              5 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: