Jira server throws column name SQLException on upgrade or installation
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
Jira server throws column name SQLException on upgrade or installation.
Solution
Symptoms
Database Server used is Microsoft SQL Server
The following appears in the
atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
java.sql.SQLException: Invalid column name '<column_name>'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1166)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1119)Diagnosis and Cause
Identify the collation used for the JIRA database in MS SQL Server by executing the following SQL query and substituting JIRADB with the database used in your installation. The name of the database could be identified from the database configuration file at $JIRA_HOME/dbconfig.xml.
1
SELECT name, collation_name FROM sys.databases WHERE name='JIRADB';The recommended collation for the JIRA database in MS SQL Server is SQL_Latin1_General_CP437_CI_AI. The SQL Exception occurs due to collation problems
When an case sensitive collation is used. The text "_CS_" in the collation name indicates case sensitive collation instead of "_CI" for a case insensitive one.
The exception is also observed with accent sensitive – indicated by "AS" – collations like
Turkish_CI_AS.
Resolution
Option 1
Change the database collation to the recommended SQL_Latin1_General_CP437_CI_AI using the following Microsoft documentation:
Microsoft SQL Server 2016: Set or change the database collation
Microsoft SQL Server 2012: Set or change the database collation
Microsoft SQL Server 2008 R2: Set or change the database collation
Microsoft SQL Server 2008: Set or change the database collation
Microsoft SQL Server 2005: Set or change the database collation
Option 2
Create a new database for JIRA using the recommended collation SQL_Latin1_General_CP437_CI_AI using the following documentation:
Configure JIRA to use this database and re-try the installation or upgrade.
Was this helpful?