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

DB2 raises errors on startup if you use a schema name that matches the start of table names e.g. JIRA

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      On DB2, If you create a scheme JIRA, during startup tables with names that start with JIRA will not be found even though the tables exist: 

      2009-06-30 13:20:10,827 main [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE JIRA.jiraworkflows (ID DECIMAL(18,0) NOT NULL, workflowname VARCHAR(255), creatorname VARCHAR(255), DESCRIPTOR CLOB, ISLOCKED VARCHAR(60), CONSTRAINT PK_jiraworkflow PRIMARY KEY (ID))
Error was: com.ibm.db2.jcc.b.nm: DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=JIRA.JIRAWORKFLOWS;TABLE, DRIVER=3.50.152
2009-06-30 13:20:10,829 main [core.entity.jdbc.DatabaseUtil] Table named "JIRAACTION" exists in the database but has no corresponding entity
2009-06-30 13:20:10,829 main [core.entity.jdbc.DatabaseUtil] Table named "JIRADRAFTWORKFLOWS" exists in the database but has no corresponding entity
2009-06-30 13:20:10,829 main [core.entity.jdbc.DatabaseUtil] Table named "JIRAEVENTTYPE" exists in the database but has no corresponding entity
2009-06-30 13:20:10,829 main [core.entity.jdbc.DatabaseUtil] Table named "JIRAISSUE" exists in the database but has no corresponding entity
2009-06-30 13:20:10,829 main [core.entity.jdbc.DatabaseUtil] Table named "JIRAPERMS" exists in the database but has no corresponding entity
2009-06-30 13:20:10,830 main [core.entity.jdbc.DatabaseUtil] Table named "JIRAWORKFLOWS" exists in the database but has no corresponding entity

      All the other tables that don't begin with JIRA will be found correctly. This does not affect the operation of JIRA - it will still work correctly.

      This seems specific to DB2, postgresql doesn't exhibit the same behaviour.

              Unassigned Unassigned
              andrew.myers Andrew Myers [Atlassian]
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: