'Data size bigger than max size for this type' Error when Importing on Oracle
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
Symptoms
During a data import, the following error appears:
1
2
org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while setting value: (Data size bigger than max size for this type: 19616)
at org.ofbiz.core.entity.jdbc.SqlJdbcUtil.setValue(SqlJdbcUtil.java:684)
Alternatively, the error code ORA-17070 may occur.
Cause
Older Oracle drivers are unable to manage the data type Workflows, issue fields and comments are saved in, if these are longer than 4000 characters. Newer versions contain a workaround that requires explicit activation in the DataSource connection properties: SetBigStringTryClob
Some versions of Oracle XE present this problem in spite of the SetBigStringTryClob flag.
Resolution
For a Tomcat hosted instance, add
SetBigStringTryClob=trueto theconnectionPropertiesattribute:1 2 3 4 5 6 7<Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource" ... driverClassName="oracle.jdbc.driver.OracleDriver" ... connectionProperties="SetBigStringTryClob=true" ... />Verify the recommended Oracle driver version is installed (see Connecting JIRA to Oracle)
Make sure the
oracle10gfield-type name is set in theentityengine.xmlStop JIRA
Drop and recreate the database
Restart JIRA and re-import the XML backup
Was this helpful?