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

Exception thrown during upgrade: Invalid object name 'jiraeventtype'

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Medium Medium
    • None
    • 6.3, 6.3.15, 7.0.10
    • Installation
    • 6.03
    • 15
    • Severity 2 - Major
    • Hide
      Atlassian Update – 31-10-2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, has a viable workarounds, so it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Won't Fix.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 31-10-2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, has a viable workarounds, so it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Won't Fix . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ignat Alexeyenko Jira Bugmaster

      Error when attempting to upgrade JIRA

      Symptoms:

      The following appears in JIRA's logs:

      2014-08-01 10:33:05,318 main INFO      [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Insert sequence for event type
2014-08-01 10:33:05,322 main ERROR      [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: Invalid object name 'jiraeventtype'.
java.sql.SQLException: Invalid object name 'jiraeventtype'.
	at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
	at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
	at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
	at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
	at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
	at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:776)
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
	at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
	at com.atlassian.jira.upgrade.tasks.util.Sequences.update(Sequences.java:36)
	at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build6320.doUpgrade(UpgradeTask_Build6320.java:41)

      Cause:

      Upgrade tasks that update sequences do not correctly apply schema name to table when the schema is named "jira". This has recently been triggered by an upgrade task in JIRA 6.3, however it's possible it could affect any future upgrade tasks which contain an update to a sequence.

      Steps to reproduce

      1. Install a version of JIRA earlier than JIRA 6.3 on MS SQL Server, making sure that the schema JIRA is installed in is called "jira", and the default schema of the user JIRA connects to MS SQL Server is something other than "jira", for example "dbo" (which is the default). JIRA actually encounters problems if the default schema is not set to "dbo".
      2. Make sure it's all working fine
      3. Upgrade to 6.3 or above
      4. Watch the atlassian-jira.log file for the error above

      Workaround:

      One of the following works around the issue:

      Option 1

      1. Change schema name to something other than "jira". Update the dbconfig.xml file according to the changes.

      Option 2

      1. Stop JIRA
      2. Change the default schema of the database user JIRA is using to be "jira"
      3. Start JIRA
      4. Allow the uprade task to complete - some things in JIRA will be broken such as the streams plugin
      5. Stop JIRA
      6. Remove the directories <jira-home>/plugins/bundled-plugins and <jira-home>/plugins/.osgi-plugins
      7. Change the default schema back to "dbo"
      8. Start JIRA
      9. JIRA should be working again

      Related Content

      This issue appears to be related to JRA-25270

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: