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

Can't specify a explicit Oracle schema in the dbconfig.xml that is also a prefix of a JIRA table name

    XMLWordPrintable

Details

    • 4.04
    • 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

      NOTE: This problem will not occur if you follow JIRA's recommended Oracle configuration to leave the "schema-name" blank. In this case JIRA will use the DB user's own schema.

      1. Connect to Oracle as "jira". All the DB tables should be created.
      2. Stop JIRA.
      3. Edit "dbconfig.xml" and set "schema-name" to "JIRA" (the uppercase is important and correct).
      4. (BUG) Start JIRA. You will get:
      2011-11-08 21:24:18,957 main WARN      [core.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database
2011-11-08 21:24:18,987 main ERROR      [core.entity.jdbc.DatabaseUtil] Could not create table "JIRA.jiraaction"
2011-11-08 21:24:18,987 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

      Note that this is only for tables that start with the schema-name "JIRA".

      You can also get a similar error if you try an connect to the "JIRA" schema as a different user. For example, lets say that "safeuser" has permission to all the tables in the "JIRA" schema. Now lets say that JIRA is configured to connect to Oracle as "safeuser" but has the schema-name set to "JIRA". JIRA will attempt to create any tables that start with "JIRA" as "safeuser" in the "JIRA" schema which the user probably wont have permission to do. In this case you end up with:

      2011-11-08 21:32:38,658 main WARN      [core.entity.jdbc.DatabaseUtil] Entity "ChangeGroup" has no table in the database
2011-11-08 21:32:38,662 main ERROR      [core.entity.jdbc.DatabaseUtil] Could not create table "JIRA.changegroup"
2011-11-08 21:32:38,663 main ERROR      [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE JIRA.changegroup (ID NUMBER(18,0) NOT NULL, issueid NUMBER(18,0), AUTHOR VARCHAR2(255), CREATED DATE, CONSTRAINT PK_changegroup PRIMARY KEY (ID))
Error was: java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges

      Attachments

        Activity

          People

            Unassigned Unassigned
            bbain bain
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: