Data too long for column error during Crowd Upgrade
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
Crowd upgrade from 1.X to 2.X is failing with errors:
1
2
3
4
5
6
7
Caused by: java.sql.BatchUpdateException: Data truncation: Data too long for column 'display_name' at row 1
at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:1269)
at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:955)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246)
Cause
The database schema changed in Crowd 2.0. There may be some columns with excessively long values that will not fit into the new schema.
Resolution
This is usually not a problem as most names are not long enough to cause this problem. Check for any extremely long data values, particularly in the column referenced in the error.
Was this helpful?