Could not create table due to missing Field Type definition
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
Problem
When installing or upgrading Jira, one or more tables may fail to be created and present messages such as below on atlassian-jira.log
.
1
2
3
2015-08-18 08:32:23,275 localhost-startStop-1 WARN [core.entity.jdbc.DatabaseUtil] Entity "ClusteredJob" has no table in the database
2015-08-18 08:32:23,275 localhost-startStop-1 ERROR [core.entity.jdbc.DatabaseUtil] Could not create table "clusteredjob"
2015-08-18 08:32:23,275 localhost-startStop-1 ERROR [core.entity.jdbc.DatabaseUtil] Field type [null] not found for field [parameters] of entity [ClusteredJob], not creating table.
Cause
This occurs when JIRA is unable to locate a field type definition for the type of data stored in a certain column of the database. This information is stored on the fieldtype-<db-type>.xml
file (located under <JIRA_INSTALL>/atlassian-jira/WEB-INF/classes/entitydefs/
).
Resolution
Option 1
Replace the fieldtype-<db-type>.xml
file with the one from a clean installation of Jira.
Option 2
Open the
entitymodel.xml
file (located on the same folder as thefieldtype-<db-type>.xml
);Locate the
field
definition according to what was presented in the log message/s (see example below) and take note of the value fortype
;1
<field name="parameters" type="byte-array" />
Open the
fieldtype-<db-type>.xml
file (according to the database driver you use) and locate thefield-type-def
property for the field noted above (see example fororacle10g
);1
<field-type-def type="byte-array" sql-type="LONG RAW" java-type="java.lang.Object"></field-type-def>
Compare with the
fieldtype-<db-type>.xml
of a new installation of Jira and add the definition for such field type;Restart Jira;
Was this helpful?