Details
Low Description
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
- Install or upgrade to Jira 9.11.0 with Oracle database.
- 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
