Fix SQL Exception on Jira Startup Due to Invalid or Missing Schema
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Upon Jira starting up, the following errors are present in atlassian-jira.log:
2007-02-05 16:54:53,112 main WARN [core.entity.jdbc.DatabaseUtil] Entity "ColumnLayoutItem" has no table in the database
2007-02-05 16:54:53,114 main ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "columnlayoutitem"
2007-02-05 16:54:53,114 main ERROR [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE columnlayoutitem (ID NUMERIC NOT NULL, COLUMNLAYOUT NUMERIC, FIELDIDENTIFIER NVARCHAR(255), HORIZONTALPOSITION NUMERIC, CON
STRAINT PK_columnlayoutitem PRIMARY KEY (ID))
Error was: java.sql.SQLException: There is already an object named 'columnlayoutitem' in the database.Solution
Cause
The dbconfig.xml file is missing the <schema-name> value. During startup, Jira tries to verify that the table exists - as it does not know what schema to check for, it will be unable to verify the table exists. Jira then tries to recreate the table, and the above exception occurs.
Resolution
If the schema is not specific, MS SQL will default to dbo, which is not the recommended schema. To fix this, please refer to the steps in Incorrect MS SQL Schema Used.
Was this helpful?