JIRA Upgrade Fails Due to Invalid Database Configuration
Symptoms
Starting JIRA with Oracle database integrated fails with exception:
2008-04-03 14:17:22,946 main [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
ALTER TABLE jiraaction ADD UPDATED DATETIME
Error was: java.sql.SQLException: ORA-00902: invalid datatype
....
2008-04-03 14:17:23,394 main [core.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
CREATE TABLE trustedapp (ID DECIMAL(18,0) NOT NULL, APPLICATION_ID VARCHAR(255), NAME VARCHAR(255), PUBLIC_KEY TEXT, IP_MATCH TEXT, URL_MATCH TEXT, TIMEOUT DECIMAL(18,0), CREATED DATETIME, CREATED_BY VARCHAR(255), UPDATED DATETIME, UPDATED_BY VARCHAR(255), CONSTRAINT PK_trustedapp PRIMARY KEY (ID))
Error was: java.sql.SQLException: ORA-00902: invalid datatype
....
CREATE TABLE worklog (ID DECIMAL(18,0) NOT NULL, issueid DECIMAL(18,0), AUTHOR VARCHAR(255), grouplevel VARCHAR(255), rolelevel DECIMAL(18,0), worklogbody LONGTEXT, CREATED DATETIME, UPDATEAUTHOR VARCHAR(255), UPDATED DATETIME, STARTDATE DATETIME, timeworked DECIMAL(18,0), CONSTRAINT PK_worklog PRIMARY KEY (ID))
Error was: java.sql.SQLException: ORA-00902: invalid datatype
....
Cause
JIRA is connecting to the Oracle database but the field-type of database in the /edit-webapp/WEB-INF/classes/entityengine.xml is configured with a different database type.
This causes JIRA to create columns in the database with incorrect Oracle data type.
Resolution
Modify the field-type to the corresponding database in the entityengine.xml datasource. You will need to update this tag for your installation:
<datasource name="defaultDS" field-type-name="oracle10g"
For more information see Connecting JIRA to Oracle.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.