Alarm message too long in UIM causes Spectrum to crash with spectrumgtw integration

Document ID : KB000118810
Last Modified Date : 01/11/2018
Show Technical Document Details
Spectrum and UIM integration with spectrumgtw probe may cause Spectrum OC to crash as UIM alarms are too large for Spectrum database.

OC Tomcat log in Spectrum may have the following error:

(SRM/AlarmHandler/bucketReader) (SRM_Alarms) - (ERROR) - Failed to add new alarmtitle record Caused by: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [INSERT INTO alarmtitle (cause_id, title) VALUES (?, ?)]; Data truncation: Data too long for column 'title' at row 1; nested exception is com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'title' at row 1
UIM 8.51
Spectrum 10.2.3
spectrumgtw 8.56
This issue is caused due to a data size mismatch between the NAS_ALARMS.message field in UIM and the alarmtitle.title in Spectrum.
The current solution on Spectrum side is to increase the alarm title on the alarm table size to 4000 chars to accommodate the "message" field of NAS_ALARMS table, which is defined as varchar(4000).

The article KB000039767 covers this configuration change:
Additional Information:
This issue has been seen especially with probes that read Windows Event log messages, such as the ntevl probe. Configuring the alarm message to capture only what is important from the entire event log should avoid this issue.