User gets a general error if list of seen entries grows too large in Novell Vibe

A user may encounter a general error with the following details if/when his list of seen entries exceeds the maximum allowed by the database column seenMap:

class.org.springframework.dao.DataIntegrityViolationException
could not update: [org.kablink.teaming.domain.SeenMap#XXX]; SQL [update SS_SeenMap set seenMap=? where principalId=?]; nested exception is org.hibernate.exception.DataException: could not update: [org.kablink.teaming.domain.SeenMap#XXX]

This error is seen with Teaming/Vibe installations running MySQL database. To fix this error the database column needs to be updated to LONGBLOB to accommodate larger data. To update the MySQL database column, follow these steps:

1. Open a command prompt on the MySQL database server and connect to the database as user 'root'
   mysql -uroot -p
   <You will be prompted to enter the password for MySQL user root>
   
   
2. Issue the following statement to connect to the Teaming/Vibe database
   use sitescape;
   
   
3. Issue the following statement to change the column type to LONGBLOB
   ALTER TABLE SS_SeenMap MODIFY COLUMN seenMap LONGBLOB NOT NULL;
   
   
4. To confirm that your changes were successful, use the following statement and check the value of column 'Type' for the field 'seenMap' (it should now be set to LONGBLOB)
   DESC SS_SeenMap;
   
   
5. If no errors are reported, your column has been updated and it is safe to exit using the command
   exit

Starting with Novell Vibe OnPrem 3.1, a fix was incorporated to prevent a user from getting in this situation. However, if you come across this issue, running the above MySQL statement will resolve the issue moving forward.

If you need further help on this issue, please contact the Novell Technical Support.