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

Oracle tables are incorrectly checked on startup

    XMLWordPrintable

Details

    • 4.03
    • Severity 3 - Minor
    • Hide
      Atlassian Update – 04 December 2017

      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, 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 Time Out.

      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 – 04 December 2017 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, 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 Time Out . 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

    Description

      This issue affects Jira installations that use Oracle for their backend.

      When Jira starts, it checks to see if the Jira tables exist in the database. If they don't exist, it attempts to create new ones. The table names are being incorrectly referenced so Jira thinks that the tables don't exist, and tries to create new ones but is denied because they do already exist.

      As an example, this is in my log file for the JIRAACTION table:

      2011-07-21 13:46:46,683 main WARN [core.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database
      2011-07-21 13:46:46,852 main ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "JIRA.jiraaction"
      2011-07-21 13:46:46,853 main ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
      CREATE TABLE JIRA.jiraaction (ID NUMBER(18,0) NOT NULL, issueid NUMBER(18,0), AUTHOR VARCHAR2(255), actiontype VARCHAR2(255), actionlevel VARCHAR2(255), rolelevel NUMBER(18,0), actionbody CLOB, CREATED DATE, UPDATEAUTHOR VARCHAR2(255), UPDATED DATE, actionnum NUMBER(18,0), CONSTRAINT PK_jiraaction PRIMARY KEY (ID))
      Error was: java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object
      ...
      2011-07-21 13:46:46,932 main WARN [core.entity.jdbc.DatabaseUtil] Table named "JIRAACTION" exists in the database but has no corresponding entity

      It seems like Jira might be looking up the JIRAACTION table in SYS.ALL_TABLES using lower case (jiraaction) which is incorrect in Oracle - it stores all table names as upper case when referenced as a part of a string (inside quotes).

      i.e. SELECT * FROM SYS.ALL_TABLES WHERE TABLE_NAME = 'JIRAACTION' AND OWNER = 'JIRA'

      Only when referencing a table directly is case-sensitivity not important.

      I'm not certain that SYS.ALL_TABLES is the method you use to look up tables however there is definitely a problem here with case.

      Attachments

        Activity

          People

            Unassigned Unassigned
            8f10b3fbba97 Miles Jordan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: