JIRA Documentation

JIRA 6.3 EAP
JIRA 6.0 Documentation
JIRA 5.2 Documentation
JIRA 5.1 Documentation
More...
 

 

Search the Knowledge Base and Documentation Spaces

You're visiting the JIRA Knowledge Base. Visit the JIRA Knowledge Base Home for an overview.

Skip to end of metadata
Go to start of metadata

Symptoms

When restoring an XML backup, (possibly during migrations to Oracle from other DBMS) the import can fail with an ORA-01461 SQL error:

or

Cause

In fieldtype-oracle10g.xml, "very-long" is defined as a VARCHAR(4000) which often can be insufficient to store the desired information. Any entity field that is defined as such in the entitymodel.xml can potentially contain large enough data is susceptible to the problem.

Resolution

There are two possible solutions:

  1. Modify $JIRA-Installation-Directory\atlassian-jira\WEB-INF\classes\entitydefs\WEB-INF/classes/entitydefs/fieldtype-oracle10g.xml to define very-long as a CLOB.
    OR
  2. Increase the size of the particular field in $JIRA-Installation-Directory/WEB-INF/classes/entitydefs/entitymodel.xml to use extremely-long which is CLOB by default.

(info) In either case, drop and re-create the database to have JIRA re-populate the schema with the new definitions (or manually move the data to another table with the new definition and swap it with the previously defined object).

Related Content

 Expand to see related content
Help us improve!
Is this article helpful?
Is the content complete?
Is it well written?