MS SQL Server 2000 Startup errors

All Versions

JIRA 4.0 Beta Documentation

Index
Please refer to our Knowledge Base article on the topic.

A user reports getting errors like these every time JIRA starts up:

[core.entity.jdbc.DatabaseUtil] Entity "Action" has no table in the database
2003-11-06 09:33:45,265 ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "jiraaction"
2003-11-06 09:33:45,265 ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE jiraaction (ID NUMERIC NOT NULL, issueid NUMERIC, AUTHOR VARCHAR(255), actiontype VARCHAR(255), actionlevel VARCHAR(255), actionbody TEXT, CREATED DATETIME, actionnum NUMERIC, CONSTRAINT PK_jiraaction PRIMARY KEY (ID))
Error was: java.sql.SQLException: There is already an object named 'jiraaction' in the database.
2003-11-06 09:33:45,265 WARN [core.entity.jdbc.DatabaseUtil] Entity "ChangeGroup" has no table in the database
2003-11-06 09:33:45,265 ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "changegroup"

JIRA functions correctly otherwise.

A solution is suggested in this jira-user post:

Hi Jason,

I have had the same errors when at startup that you are seeing.

The problem on my server was that when the user in my database ('JIRA')
created tables they were created as dbo.<tablename> and not
JIRA.<tablename>
so when JIRA attempts to verify a table JIRA.<tablename> exists it fails.
Then it tries to create <tablename>, but it already exists. All the
created
tables are owned by 'dbo' and not 'JIRA'.

I am running on Microsoft SQL Server so my fix may not fit exactly but this
is what I had to do:
Create the 'JIRA' user as a regular user of the JIRA database. Add the
JIRA user to the db_owner (database owner) role. (DO NOT change the database
owner to 'JIRA', just add the role!)

Of course, you will have to drop your existing database first.

Cheers,
Bradley.

We have also had reports from other users that there are also alternatives to this solution. The ddl_admin, db_datareader and db_datawriter roles could be used instead of db_owner role for the jirauser account.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (1)

 

  1. Feb 02

    Neil Harrington says:

    I just dealt with the same problem, but with SQL Server 2005, when I was trying ...

    I just dealt with the same problem, but with SQL Server 2005, when I was trying to upgrade from Jira version 3.6.5 to 3.13.1

    However, instead of just having unhelpful information in the log file, it would not upgrade. I figure the reason was that it tried to find the table, did not find it and therefore tried to create it (ultimately, failing). As such, it did not add the new columns in and when it came time to export, it just didn't work.

    In order to get around it, I changed did two things.

    1. changed the login properties of the Jira User, to have a default Schema of the Jira User (in my case, JiraUser), and role membership of db_owner
    2. changed all the tables so that the object owner was the Jira user.  The way to do this for the jiraaction table is: 
       sp_changeobjectowner 'jiraaction',  'JiraUser'

    Note: I tried setting the db_datareader, db_datawriter and db_ddladmin roles instead of db_owner, but that did not work.

Add Comment


Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.