Hi Folks,
I have upgraded the JIRA 7.0 to 7.13 but can see below error in logs.
---------------------------------------------------------------------------------
TOTAL : Used: 696 MiB. Committed: 956 MiB. Max: 2259 MiB
---------------------------------------------------------------------------------
2019-02-04 22:11:26,552 Caesium-1-4 INFO [c.a.jira.startup.CacheWarmerLauncher] Warming up 3 caches.
2019-02-04 22:11:48,013 Caesium-1-4 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 21460 ms.
2019-02-04 22:12:11,241 Caesium-1-2 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2019-02-04 22:12:11,295 Caesium-1-2 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2019-02-04 22:12:12,770 Caesium-1-2 ERROR [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Upgrade task [host,buildNumber=73011] failed
com.querydsl.core.QueryException: Caught SQLSyntaxErrorException for insert into OS_CURRENTSTEP (ID, ENTRY_ID, STEP_ID, ACTION_ID, OWNER, START_DATE, DUE_DATE, FINISH_DATE, STATUS, CALLER)
select hs.ID, hs.ENTRY_ID, hs.STEP_ID, hs.ACTION_ID, hs.OWNER, hs.START_DATE, hs.DUE_DATE, null, hs.STATUS, hs.CALLER
from OS_HISTORYSTEP hs
where hs.ENTRY_ID in (?, ?,
at java.lang.Thread.run(Thread.java:748)
Caused by: java.sql.SQLSyntaxErrorException: ORA-00904: "HS"."ENTRY_ID": invalid identifier
Hi Grigory,
I found the same configuration:
Database configuration OK
___ Database Configuration _________________
Loading entityengine.xml from : file:/opt/atlassian/jira/atlassian-jira/WEB-INF/classes/entityengine.xml
Entity model field type name : oracle10g
Entity model schema name :
Database Version : Oracle - Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options
Database Driver : Oracle JDBC driver - 11.2.0.2.0
Do you say that JIRA 7.13 does not support Oracle 11 and needs Oracle 12C ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here's the reply to the similar question by @Andy Heinzer from the Atlassian Team:
I have seen this specific error happen on Jira instances that are still running an Oracle 11g or earlier database. Jira 7.x.x versions do have support for Oracle databases, but only 12c versions. This is documented in the Supported Platforms docs.
Yes, it seems so.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.