Scan fails with Data too long for column 'NAME_' error

[#1]

Summary

This article discusses the cause of an issue with the maximum character count on the PSE_SCANNED_ITEMS.NAME column

Symptoms

Scans which include long file paths such as archives can fail with the below error being shown in the scanEngineDetail.log:

Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'NAME_' at row 1
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3968)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3906)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2524)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2677)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2549)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2073)
at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2009)
at com.mysql.jdbc.PreparedStatement.executeLargeUpdate(PreparedStatement.java:5098)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1994)

Resolution

A bug for this issue has been reported under reference SCA-8909. A permanent resolution to this issue will be added to the 6.12.2 release which will increase the maximum character count for the PSE_SCANNED_ITEMS_NAME_ column from 255 to 512.